develooper Front page | perl.perl5.porters | Postings from April 2010

Re: [perl #74706] [PATCH] Eliminate `git pull upstream blead` in favor of remote.*.pushurl

Thread Previous | Thread Next
From:
David Golden
Date:
April 28, 2010 06:33
Subject:
Re: [perl #74706] [PATCH] Eliminate `git pull upstream blead` in favor of remote.*.pushurl
Message ID:
j2m5d4beb41004280633o7813842dyf1484c4515993968@mail.gmail.com
On Tue, Apr 27, 2010 at 3:46 PM, Ævar Arnfjörð Bjarmason
<perlbug-followup@perl.org> wrote:
> # New Ticket Created by  "Ævar Arnfjörð Bjarmason"
> # Please include the string:  [perl #74706]
> # in the subject line of all future correspondence about this issue.
> # <URL: http://rt.perl.org/rt3/Ticket/Display.html?id=74706 >
>
>
> remote.*.pushurl was introduced in v1.6.4 and makes managing cases
> like these much easier. Users hip enough to use GitHub are probably
> hip enough to have Git 1.6.4 or later.

My personal bias is that we want to give instructions that favor
clarity over brevity.

I would rather see "git pull" and "git push" have explicit remotes and
branches listed in a guide like this. If people want to apply their
own git expertise to take shortcuts, that's fine, but if we want the
documentation to be as helpful as possible to people with a very wide
range of expertise, being explicit is a better teaching tool.

I'd support pointing people to some external documentation about
taking shortcuts, but wouldn't want them to be in the perlrepository.

Also -- if consensus winds up in favor -- I have a concern that the
patch as given depends on the exact ordering of the git config
statements.  I would suggest using a literal for the configuration of
remote.origin.pushurl rather than picking it up from the previously
configured value.

-- David

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About