From: "François Revol" <revol@free.fr>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Branch/tag renames in git
Date: Wed, 29 Apr 2009 00:24:02 +0200 CEST [thread overview]
Message-ID: <18796329628-BeMail@laptop> (raw)
In-Reply-To: <alpine.DEB.1.00.0904290011130.10279@pacific.mpi-cbg.de>
> Hi,
>
> On Tue, 28 Apr 2009, Anthony Liguori wrote:
>
> > Based on the previous discussion, I've renamed the branches tags in
> > git.
> > It doesn't look like a git pull automatically cleans up the old
> > branches/tags which is somewhat unfortunate.
>
> Git complaints should be sent to git@vger.kernel.org, not hidden in
> some
> mailing list only one Git developer reads (and that only when time
> permits).
You can even send them a patch, if you get it to work...
:^)
François.
prev parent reply other threads:[~2009-04-28 22:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 21:29 [Qemu-devel] Branch/tag renames in git Anthony Liguori
2009-04-28 21:42 ` François Revol
2009-04-28 21:58 ` François Revol
2009-04-28 22:04 ` Anthony Liguori
2009-04-28 22:08 ` François Revol
2009-04-28 22:12 ` Johannes Schindelin
2009-04-28 22:24 ` François Revol [this message]
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=18796329628-BeMail@laptop \
--to=revol@free.fr \
--cc=Johannes.Schindelin@gmx.de \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.