On 02/07/2019 20:24, Theodore Ts'o wrote:
I think the real problem with all of this feature request is that it's
all presuming a particular workflow, and git is currently*not*
strongly opinionated about the workflow.
I'd suggest that git does have a clear preference for a workflow that is
based
On Tue, Jul 02, 2019 at 11:52:35AM -0700, Bryan Turner wrote:
> Sorry, I should have clarified my "--no-track" in my original message
> when I provided the example. I did "--no-track" because if I push
> "bturner-some-bugfix" to a server, I'm likely going to do something
> like "git push -u origin
On Tue, Jul 2, 2019 at 10:36 AM Junio C Hamano wrote:
>
> In this whole thread, I have been wondering if I am missing
> something crucial, but now I am deeply puzzled why after many people
> made comments, nobody raises a question about the "--no-track" thing
> in the early message in the thread.
Philip Oakley writes:
>> I suspect the question is in regards to "What branch did I create
>> my local branch from?", especially given the pull request
>> reference.
>>
>> In other words, when I locally do:
>> git checkout --no-track -b bturner-some-bugfix origin/release/5.16
>>
>> release/5.16 i
On 01/07/2019 21:12, rsbec...@nexbridge.com wrote:
On July 1, 2019 3:48 PM, Bryan Turner wrote:
On Mon, Jul 1, 2019 at 12:35 PM Junio C Hamano wrote:
Eric Kulcyk writes:
[Overly long lines are not appreciated around here.]
We would like to track parent branches so that creating pull
request
On Mon, 01 Jul 2019 12:48:16 +, Bryan Turner wrote:
...
> In other words, when I locally do:
> git checkout --no-track -b bturner-some-bugfix origin/release/5.16
>
> release/5.16 is the "parent branch" of my bugfix branch and, when I
> push my branch and try to open a pull request, release/5.1
its...@pobox.com; git@vger.kernel.org
Subject: Re: Tracking parent branches in Git
> > [Overly long lines are not appreciated around here.]
Thanks for the feedback, is there an email client or tool
that can format the lines correctly?
> >
> > > We would like
ead of doing this in
> core git because of the transient nature of the relationship between a branch
> and a commit.
Multiple branches can have the same commit, but only one branch can
be checked out at once, right? Then the parent branch would be the
branch you were on when you ran checkout -b
On Mon, Jul 01, 2019 at 12:48:16PM -0700, Bryan Turner wrote:
> Since branches are ephemeral names and have no intrinsic metadata of
> their own (unlike, say, annotated tags or commits), I suspect
> implementing something like this may be more complicated than it might
> initially appear, especiall
On July 1, 2019 3:48 PM, Bryan Turner wrote:
On Mon, Jul 1, 2019 at 12:35 PM Junio C Hamano wrote:
>
> Eric Kulcyk writes:
>
> [Overly long lines are not appreciated around here.]
>
> > We would like to track parent branches so that creating pull
> > requests can automatically determine the corr
On Mon, Jul 1, 2019 at 12:35 PM Junio C Hamano wrote:
>
> Eric Kulcyk writes:
>
> [Overly long lines are not appreciated around here.]
>
> > We would like to track parent branches so that creating pull
> > requests can automatically determine the correct branch to merge
> > against. I understand
Eric Kulcyk writes:
[Overly long lines are not appreciated around here.]
> We would like to track parent branches so that creating pull
> requests can automatically determine the correct branch to merge
> against. I understand that this would require tracking more
> information than is currentl
Hello,
We would like to track parent branches so that creating pull requests can
automatically determine the correct branch to merge against. I understand that
this would require tracking more information than is currently available right
now in git. Also, it seems that if some cases, it is n
13 matches
Mail list logo
