git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Jakub Narebski <jnareb@gmail.com>
Subject: Re: Deleting remote branches with git-branch and reflog questions
Date: Tue, 23 Jan 2007 14:32:22 +0000	[thread overview]
Message-ID: <200701231432.24225.andyparkins@gmail.com> (raw)
In-Reply-To: <ep51ie$i23$1@sea.gmane.org>

On Tuesday 2007 January 23 13:12, Jakub Narebski wrote:

> The problem is when you delete branch 'foo', and then create branch
> 'foo/bar'. You can't have both 'foo' and 'foo/bar' reflog.

Ah; yes of course.  That is a bit of a deal breaker isn't it?

On the other hand, why delete it instantly?  Since the reflog is currently 
deleted by git-branch anyway, couldn't the deletion be delayed until the 
creation of foo/bar?  At least then the deletion only hits if it really has 
to.  In most circumstances foo then foo/bar is fairly unlikely.


Andy

-- 
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com

  reply	other threads:[~2007-01-23 14:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-23 12:59 Deleting remote branches with git-branch and reflog questions Andy Parkins
2007-01-23 13:02 ` Andreas Ericsson
2007-01-23 13:14   ` Andy Parkins
2007-01-23 21:25     ` Junio C Hamano
2007-01-23 21:35       ` Johannes Schindelin
2007-01-23 21:52       ` Nicolas Pitre
2007-01-23 22:06         ` Johannes Schindelin
2007-01-24  1:46         ` Junio C Hamano
2007-01-24  2:12           ` Nicolas Pitre
2007-01-24  2:22             ` Jakub Narebski
2007-01-24  3:18               ` Nicolas Pitre
2007-01-24  9:58             ` Johannes Schindelin
2007-01-23 13:12 ` Jakub Narebski
2007-01-23 14:32   ` Andy Parkins [this message]
2007-01-23 14:59     ` Johannes Schindelin
2007-01-23 15:29       ` Andy Parkins

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=200701231432.24225.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /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).