git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yann Dirson <dirson@bertin.fr>
To: Jeff King <peff@peff.net>
Cc: Jay Soffian <jaysoffian@gmail.com>, git@vger.kernel.org
Subject: Re: ghost refs
Date: Tue, 20 Apr 2010 16:42:25 +0200	[thread overview]
Message-ID: <20100420164225.1400c280@chalon.bertin.fr> (raw)
In-Reply-To: <20100420142444.GA8851@coredump.intra.peff.net>

Le Tue, 20 Apr 2010 10:24:44 -0400,
Jeff King <peff@peff.net> a écrit :

> On Tue, Apr 20, 2010 at 09:33:42AM -0400, Jay Soffian wrote:
> 
> > 4. Just append to the existing reflog? Given:
> > 
> > $ git checkout -b topic origin/master # 1
> > $ git add; git commit ...
> > $ git checkout master
> > $ git merge topic
> > $ git branch -d topic
> > $ git checkout -b topic origin/master # 2
> 
> I like how the user would interact with that, but what happens with:
> 
>   git checkout -b topic/subtopic
> 
> The reflog of the deleted branch is in the way.

That would be addressed by considering logs/dead_refs/* contents
*logical* continuations of logs/refs/* (bottom-most suggestion in my
other email)

-- 
Yann

  reply	other threads:[~2010-04-20 14:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 16:38 ghost refs John Dlugosz
2010-04-07 16:58 ` Avery Pennarun
2010-04-07 21:00   ` Jeff King
2010-04-07 22:00     ` John Dlugosz
2010-04-07 22:03       ` Avery Pennarun
2010-04-07 22:10         ` John Dlugosz
2010-04-07 22:11           ` Avery Pennarun
2010-04-08  4:30             ` Jeff King
2010-04-08 16:07               ` John Dlugosz
2010-04-08 16:55                 ` Junio C Hamano
2010-04-08 19:49                   ` Jeff King
2010-04-08 20:42                     ` Junio C Hamano
2010-04-08 22:14                       ` Avery Pennarun
2010-04-08 23:04                       ` Nicolas Sebrecht
2010-04-17 11:51                       ` Jeff King
2010-04-17 16:32                         ` Junio C Hamano
2010-04-17 16:57                           ` Git documentation writing guidelines (was: Re: ghost refs) Jakub Narebski
2010-04-18  0:28                             ` Git documentation writing guidelines Junio C Hamano
2010-04-19 15:33                         ` ghost refs John Dlugosz
2010-04-20  7:02     ` Yann Dirson
2010-04-20 11:51       ` Jeff King
2010-04-20 12:02         ` Zefram
2010-04-20 13:00           ` Yann Dirson
2010-04-20 13:14             ` Zefram
2010-04-20 13:33         ` Jay Soffian
2010-04-20 14:24           ` Jeff King
2010-04-20 14:42             ` Yann Dirson [this message]
2010-04-20 14:52             ` Jay Soffian
2010-04-20 15:03               ` Alex Riesen
2010-04-20 15:10               ` Jeff King

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100420164225.1400c280@chalon.bertin.fr \
    --to=dirson@bertin.fr \
    --cc=git@vger.kernel.org \
    --cc=jaysoffian@gmail.com \
    --cc=peff@peff.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).