From: Jay Soffian <jaysoffian@gmail.com>
To: git@vger.kernel.org
Cc: Jay Soffian <jaysoffian@gmail.com>, gitster@pobox.com
Subject: [PATCH 0/3] remote HEAD improvements
Date: Wed, 11 Feb 2009 01:01:20 -0500 [thread overview]
Message-ID: <1234332083-45147-1-git-send-email-jaysoffian@gmail.com> (raw)
There is currently no porcelain for dealing with remote HEADs (i.e.
$GIT_DIR/remotes/<remote>/HEAD). This series:
1) Teaches git remote a new "sethead" verb:
To set a remote HEAD explicitly:
$ git remote sethead <name> <branch>
To set a remote HEAD to match the upstream repo:
$ git remote sethead <name> -a
To delete a remote HEAD:
$ git remote sethead <name> -d
2) Teaches git remote show to display the remote HEAD:
$ git remote show origin
* remote origin
URL: git://git.kernel.org/pub/scm/git/git.git
HEAD: master
3) Documents the new sethead verb. I also correct the git remote man page
w/respect to the "-m <master>" option. The man page implied that the remote
HEAD was set automatically when adding a remote (a la git clone), but this is
not true. And, since I couldn't find anywhere else that the point of having a
remote HEAD is documented, I documented it here.
Jay Soffian (3):
builtin-remote: move duplicated cleanup code its own function
builtin-remote: teach show to display remote HEAD
builtin-remote: add sethead verb
Documentation/git-remote.txt | 20 +++++++-
builtin-remote.c | 108 ++++++++++++++++++++++++++++++++++++++---
2 files changed, 118 insertions(+), 10 deletions(-)
next reply other threads:[~2009-02-11 6:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 6:01 Jay Soffian [this message]
2009-02-11 6:01 ` [PATCH 1/3] builtin-remote: move duplicated cleanup code its own function Jay Soffian
2009-02-11 6:01 ` [PATCH 2/3] builtin-remote: teach show to display remote HEAD Jay Soffian
2009-02-11 6:01 ` [PATCH 3/3] builtin-remote: add sethead verb Jay Soffian
2009-02-12 0:26 ` [PATCH 2/3] builtin-remote: teach show to display remote HEAD Jeff King
2009-02-12 1:48 ` Jay Soffian
2009-02-12 1:56 ` Jeff King
2009-02-12 20:27 ` Daniel Barkalow
2009-02-12 21:24 ` Junio C Hamano
2009-02-12 21:34 ` Daniel Barkalow
2009-02-12 21:37 ` Jay Soffian
2009-02-12 22:55 ` Daniel Barkalow
2009-02-12 0:18 ` [PATCH 1/3] builtin-remote: move duplicated cleanup code its own function Jeff King
2009-02-12 1:44 ` Jay Soffian
2009-02-12 1:50 ` Jeff King
2009-02-12 20:13 ` Daniel Barkalow
2009-02-12 0:17 ` [PATCH 0/3] remote HEAD improvements 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=1234332083-45147-1-git-send-email-jaysoffian@gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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.