From: Junio C Hamano <junkio@cox.net>
To: Sam Vilain <sam@vilain.net>
Cc: git@vger.kernel.org
Subject: Re: [wishlist] git branch -d -r remotename
Date: Sun, 18 Mar 2007 12:42:30 -0700 [thread overview]
Message-ID: <7vvegyl4nt.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20070318113210.5843E13A382@magnus.utsl.gen.nz> (Sam Vilain's message of "Sun, 18 Mar 2007 23:01:33 +1200")
Sam Vilain <sam@vilain.net> writes:
> One time again, this time with the call to porcelain command
> `git-branch` replaced with the plumbing command `symbolic-ref HEAD`
>
> I also changed the output to be a little less "Got here\n" style.
>
> Subject: [PATCH] git-remote: implement prune -c
>
> It would be nice to prune local refs which are irrelevant; add an
> option to git-remote prune, with documentation.
I do not understand what workflow you are assuming, so your use
of the word "irrelevant" does not mean much to me. I suspect
other readers of the patch and documentation wouldn't find it
clear in what situation this option is useful.
Perhaps you are thinking about this scenario? I am only
guessing because you are not clear enough:
$ git clone
... time passes ...
$ git checkout -b next origin/next
... build, install, have fun ...
$ git checkout master
... time passes ...
$ git branch
... notice that you do not hack on your copy of 'next'
... and want to remove it
$ git remote prune -c
In any case, are you checking irrelevancy? What if your foo branch has
more changes to be sent upstream? Even when the remote has a
bit older version doesn't your code remove yours? For example,
if you did this, instead of the above, what happens?
$ git clone
... time passes ...
$ git checkout -b next origin/next
... build, install, have fun ...
... find an opportunity to improve ...
$ edit
$ git commit ;# on your 'next'.
... build, install, test ...
$ git checkout master
... time passes ...
$ git branch
... notice that you do not hack on your copy of 'next' anymore,
... and want to remove it
$ git remote prune -c
If the above is the usage scenario you are trying to help, then
wouldn't it be helpful if you could also help removing 'my-next'
in this slightly altered example?
$ git clone
... time passes ...
$ git checkout -b my-next origin/next
... build, install, have fun ...
$ git checkout master
... time passes ...
$ git branch
... notice that you do not hack on your copy of 'next'
... which is 'my-next', and want to remove it
$ git remote prune -c
next prev parent reply other threads:[~2007-03-18 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 9:36 [wishlist] git branch -d -r remotename Sam Vilain
2007-03-18 11:01 ` Sam Vilain
2007-03-18 11:01 ` Sam Vilain
2007-03-18 19:42 ` Junio C Hamano [this message]
2007-03-18 21:46 ` Sam Vilain
2007-03-19 6:18 ` Junio C Hamano
2007-03-19 6:40 ` Junio C Hamano
2007-03-19 23:37 ` (unknown) Sam Vilain
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vvegyl4nt.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=sam@vilain.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).