* git-rebase and reflog @ 2008-04-30 16:04 Ping Yin 2008-04-30 16:37 ` Jakub Narebski 0 siblings, 1 reply; 8+ messages in thread From: Ping Yin @ 2008-04-30 16:04 UTC (permalink / raw) To: Git Mailing List The history of git-rebase will go into reflog. This kind of behaviour makes me annoyed when using git-reflog where i can see so many useless intermediate log entries (generated by rebase). So how about not recording the intermediate commits to reflog? -- Ping Yin ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: git-rebase and reflog 2008-04-30 16:04 git-rebase and reflog Ping Yin @ 2008-04-30 16:37 ` Jakub Narebski 2008-04-30 16:56 ` Ping Yin 0 siblings, 1 reply; 8+ messages in thread From: Jakub Narebski @ 2008-04-30 16:37 UTC (permalink / raw) To: Ping Yin; +Cc: Git Mailing List "Ping Yin" <pkufranky@gmail.com> writes: > The history of git-rebase will go into reflog. This kind of behaviour > makes me annoyed when using git-reflog where i can see so many useless > intermediate log entries (generated by rebase). > > So how about not recording the intermediate commits to reflog? If I remember and understand it correctly, because currently rebase uses detached HEAD, the intermediate steps would go into HEAD reflog, but only final step would go into branch reflog... Please correct me if I am wrong. -- Jakub Narebski Poland ShadeHawk on #git ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: git-rebase and reflog 2008-04-30 16:37 ` Jakub Narebski @ 2008-04-30 16:56 ` Ping Yin 2008-04-30 17:05 ` Brandon Casey 0 siblings, 1 reply; 8+ messages in thread From: Ping Yin @ 2008-04-30 16:56 UTC (permalink / raw) To: Jakub Narebski; +Cc: Git Mailing List On Thu, May 1, 2008 at 12:37 AM, Jakub Narebski <jnareb@gmail.com> wrote: > > "Ping Yin" <pkufranky@gmail.com> writes: > > > The history of git-rebase will go into reflog. This kind of behaviour > > makes me annoyed when using git-reflog where i can see so many useless > > intermediate log entries (generated by rebase). > > > > So how about not recording the intermediate commits to reflog? > > If I remember and understand it correctly, because currently rebase > uses detached HEAD, the intermediate steps would go into HEAD reflog, > but only final step would go into branch reflog... > > Please correct me if I am wrong. I am also not clear about this. If your are right, how can i look over the branch reflog. I know the master@{1} syntax, but i want to see master@{1}, master@{2} until master@{n} in a single command just as how 'git reflog' shows HEAD@{1} to HEAD@{n}. -- Ping Yin ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: git-rebase and reflog 2008-04-30 16:56 ` Ping Yin @ 2008-04-30 17:05 ` Brandon Casey 2008-04-30 17:13 ` Ping Yin 0 siblings, 1 reply; 8+ messages in thread From: Brandon Casey @ 2008-04-30 17:05 UTC (permalink / raw) To: Ping Yin; +Cc: Jakub Narebski, Git Mailing List Ping Yin wrote: > If your are right, how can i look over the branch reflog. I know the > master@{1} syntax, but i want to see master@{1}, master@{2} until > master@{n} in a single command just as how 'git reflog' shows HEAD@{1} > to HEAD@{n}. Have you checked the documentation for 'git reflog'? It says: The subcommand "show" (which is also the default, in the absence of any subcommands) will take all the normal log options, and show the log of the reference provided in the command-line (or `HEAD`, by default). So, 'git reflog show master' should get you what you want. You may also want to check out the '-g' option to git-log. For example, 'git log -g master'. -brandon ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: git-rebase and reflog 2008-04-30 17:05 ` Brandon Casey @ 2008-04-30 17:13 ` Ping Yin 2008-04-30 17:22 ` Avery Pennarun 2008-04-30 17:34 ` Junio C Hamano 0 siblings, 2 replies; 8+ messages in thread From: Ping Yin @ 2008-04-30 17:13 UTC (permalink / raw) To: Brandon Casey; +Cc: Jakub Narebski, Git Mailing List On Thu, May 1, 2008 at 1:05 AM, Brandon Casey <casey@nrlssc.navy.mil> wrote: > Ping Yin wrote: > > > If your are right, how can i look over the branch reflog. I know the > > master@{1} syntax, but i want to see master@{1}, master@{2} until > > master@{n} in a single command just as how 'git reflog' shows HEAD@{1} > > to HEAD@{n}. > > Have you checked the documentation for 'git reflog'? > > It says: > > The subcommand "show" (which is also the default, in the absence of any > subcommands) will take all the normal log options, and show the log of > the reference provided in the command-line (or `HEAD`, by default). > > So, 'git reflog show master' should get you what you want. Oh, i missed that. Maybe we should add an example section. > > You may also want to check out the '-g' option to git-log. For example, > 'git log -g master'. Oh, wonderful. However, i still think the intemediate commits of git-rebase needn't go into HEAD's reflog because it's totally useless. -- Ping Yin ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: git-rebase and reflog 2008-04-30 17:13 ` Ping Yin @ 2008-04-30 17:22 ` Avery Pennarun 2008-04-30 17:34 ` Junio C Hamano 1 sibling, 0 replies; 8+ messages in thread From: Avery Pennarun @ 2008-04-30 17:22 UTC (permalink / raw) To: Ping Yin; +Cc: Brandon Casey, Jakub Narebski, Git Mailing List On 4/30/08, Ping Yin <pkufranky@gmail.com> wrote: > However, i still think the intemediate commits of git-rebase needn't > go into HEAD's reflog because it's totally useless. I don't know, I can imagine a situation where I'm doing a rebase, I get a conflict, I type the wrong command, and so I lose a bunch of my intermediate work because I was an idiot. The reflog sounds like it would be helpful here as much as anywhere. Have fun, Avery ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: git-rebase and reflog 2008-04-30 17:13 ` Ping Yin 2008-04-30 17:22 ` Avery Pennarun @ 2008-04-30 17:34 ` Junio C Hamano 2008-04-30 17:38 ` Ping Yin 1 sibling, 1 reply; 8+ messages in thread From: Junio C Hamano @ 2008-04-30 17:34 UTC (permalink / raw) To: Ping Yin; +Cc: Brandon Casey, Jakub Narebski, Git Mailing List "Ping Yin" <pkufranky@gmail.com> writes: > However, i still think the intemediate commits of git-rebase needn't > go into HEAD's reflog because it's totally useless. Actually I use it from time to time when I need to compare intermediate steps of _previous_ run of the same rebase while rebasing, if the current run needs to resolve conflicts (may be the same conflict, may be a different conflict, depending on what bases are used for the current run and the previous run). Please do not break it. ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: git-rebase and reflog 2008-04-30 17:34 ` Junio C Hamano @ 2008-04-30 17:38 ` Ping Yin 0 siblings, 0 replies; 8+ messages in thread From: Ping Yin @ 2008-04-30 17:38 UTC (permalink / raw) To: Junio C Hamano; +Cc: Brandon Casey, Jakub Narebski, Git Mailing List On Thu, May 1, 2008 at 1:34 AM, Junio C Hamano <gitster@pobox.com> wrote: > "Ping Yin" <pkufranky@gmail.com> writes: > > > > However, i still think the intemediate commits of git-rebase needn't > > go into HEAD's reflog because it's totally useless. > > Actually I use it from time to time when I need to compare intermediate > steps of _previous_ run of the same rebase while rebasing, if the current > run needs to resolve conflicts (may be the same conflict, may be a > different conflict, depending on what bases are used for the current run > and the previous run). OK, i'm wrong, it is a useful case. -- Ping Yin ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2008-04-30 17:39 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2008-04-30 16:04 git-rebase and reflog Ping Yin 2008-04-30 16:37 ` Jakub Narebski 2008-04-30 16:56 ` Ping Yin 2008-04-30 17:05 ` Brandon Casey 2008-04-30 17:13 ` Ping Yin 2008-04-30 17:22 ` Avery Pennarun 2008-04-30 17:34 ` Junio C Hamano 2008-04-30 17:38 ` Ping Yin
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox