On Thu, Dec 27, 2012 at 9:15 PM, Woody Wu wrote:
> On Mon, Dec 24, 2012 at 09:24:39AM -0800, Martin von Zweigbergk wrote:
>> On Sun, Dec 23, 2012 at 11:31 PM, Woody Wu wrote:
>> >
>> > This is not working to me since I have more than one local branch that
>> > diverged from the master, and in fac
On Mon, Dec 24, 2012 at 09:24:39AM -0800, Martin von Zweigbergk wrote:
> On Sun, Dec 23, 2012 at 11:31 PM, Woody Wu wrote:
> > On Sun, Dec 23, 2012 at 11:09:58PM -0500, Seth Robertson wrote:
> >>
> >> In message <20121224035825.GA17203@zuhnb712>, Woody Wu writes:
> >>
> >> How can I find out w
On Tue, Dec 25, 2012 at 2:10 AM, Junio C Hamano wrote:
>> I looked briefly at reflog before writing my previous mail and noticed
>> that when I create a new branch (usually using "git checkout -b branch
>> ref") it does not record the base commit.
>
> Hmph. Perhaps you are referring to something
Nguyen Thai Ngoc Duy writes:
> On Mon, Dec 24, 2012 at 1:27 PM, Junio C Hamano wrote:
>> Nguyen Thai Ngoc Duy writes:
>>
>>> On Mon, Dec 24, 2012 at 12:34 PM, Tomas Carnecky
>>> wrote:
> Maybe we should store this information. reflog is a perfect place for
> this, I think. If this info
On Sun, Dec 23, 2012 at 11:31 PM, Woody Wu wrote:
> On Sun, Dec 23, 2012 at 11:09:58PM -0500, Seth Robertson wrote:
>>
>> In message <20121224035825.GA17203@zuhnb712>, Woody Wu writes:
>>
>> How can I find out what's the staring reference point (a commit number
>> or tag name) of a locally
On Mon, Dec 24, 2012 at 06:16:05PM +0700, Nguyen Thai Ngoc Duy wrote:
> > The reason that git does not bother storing "where did I start this
> > branch" is that it is usually not useful. The right question is usually
> > "what is the merge base". There are exceptions, of course (e.g., if you
> >
On Mon, Dec 24, 2012 at 1:27 PM, Junio C Hamano wrote:
> Nguyen Thai Ngoc Duy writes:
>
>> On Mon, Dec 24, 2012 at 12:34 PM, Tomas Carnecky
>> wrote:
Maybe we should store this information. reflog is a perfect place for
this, I think. If this information is reliably available, git reba
On Mon, Dec 24, 2012 at 1:19 PM, Jeff King wrote:
> On Mon, Dec 24, 2012 at 12:28:45PM +0700, Nguyen Thai Ngoc Duy wrote:
>
>> > You want to know "what commit was I at when I typed `git branch
>> > mybranch`"? The problem is git doesn't record this information and
>> > doesn't have the slightest
On Mon, Dec 24, 2012 at 8:31 AM, Woody Wu wrote:
> But thanks anyway, I see you guys's discussions and it's a little hard
> to understand to me at the moment. Currently, I still have to use gitk
> with narrowed outputs.
Each commit refers to it's parent. If you take a branch, and keep
following t
On Sun, Dec 23, 2012 at 11:09:58PM -0500, Seth Robertson wrote:
>
> In message <20121224035825.GA17203@zuhnb712>, Woody Wu writes:
>
> How can I find out what's the staring reference point (a commit number
> or tag name) of a locally created branch? I can use gitk to find out it
> but
Nguyen Thai Ngoc Duy writes:
> On Mon, Dec 24, 2012 at 12:34 PM, Tomas Carnecky
> wrote:
>>> Maybe we should store this information. reflog is a perfect place for
>>> this, I think. If this information is reliably available, git rebase
>>> can be told to "rebase my whole branch" instead of my ch
On Mon, Dec 24, 2012 at 12:28:45PM +0700, Nguyen Thai Ngoc Duy wrote:
> > You want to know "what commit was I at when I typed `git branch
> > mybranch`"? The problem is git doesn't record this information and
> > doesn't have the slightest clue.
>
> Maybe we should store this information. reflog
On Mon, Dec 24, 2012 at 12:34 PM, Tomas Carnecky
wrote:
>> Maybe we should store this information. reflog is a perfect place for
>> this, I think. If this information is reliably available, git rebase
>> can be told to "rebase my whole branch" instead of my choosing the
>> base commit for it.
>
>
On Mon, 24 Dec 2012 12:28:45 +0700, Nguyen Thai Ngoc Duy
wrote:
> On Mon, Dec 24, 2012 at 11:09 AM, Seth Robertson wrote:
> >
> > In message <20121224035825.GA17203@zuhnb712>, Woody Wu writes:
> >
> > How can I find out what's the staring reference point (a commit number
> > or tag name)
On Mon, Dec 24, 2012 at 11:09 AM, Seth Robertson wrote:
>
> In message <20121224035825.GA17203@zuhnb712>, Woody Wu writes:
>
> How can I find out what's the staring reference point (a commit number
> or tag name) of a locally created branch? I can use gitk to find out it
> but this met
In message <20121224035825.GA17203@zuhnb712>, Woody Wu writes:
How can I find out what's the staring reference point (a commit number
or tag name) of a locally created branch? I can use gitk to find out it
but this method is slow, I think there might be a command line to do it
qui
Hi, list
How can I find out what's the staring reference point (a commit number
or tag name) of a locally created branch? I can use gitk to find out it
but this method is slow, I think there might be a command line to do it
quickly.
Thanks in advance.
--
woody
I can't go back to yesterday - beca
17 matches
Mail list logo
