From: Finn Arne Gangstad <finnag@pvv.org>
To: git@vger.kernel.org
Subject: Pushing and fetching sha1s directly
Date: Sat, 22 Dec 2007 22:13:08 +0100 [thread overview]
Message-ID: <20071222211308.GA27281@pvv.org> (raw)
Currently there seems to be no way of pusing a sha1 directly, or to
fetch a sha1 directly. When working with submodules, it is convenient
to be able to work with detached HEADs, so it would be good if this
could be supported also by fetch and push.
What would be a resonable syntax for this? I'm thinking something like
git fetch --sha1 <repository> <sha1>
git push --sha1 <repository> <sha1>
Where <sha1> could really be a <commit> I guess, but the option name
"--commit" seems wrong somehow. Another option is to extend refspecs
so sha1s can be allowed in there directly, so this would just work:
git fetch <repository> <sha1>
What do you prefer?
- Finn Arne
next reply other threads:[~2007-12-22 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-22 21:13 Finn Arne Gangstad [this message]
2007-12-22 23:12 ` Pushing and fetching sha1s directly Junio C Hamano
2007-12-23 20:04 ` Johannes Schindelin
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=20071222211308.GA27281@pvv.org \
--to=finnag@pvv.org \
--cc=git@vger.kernel.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 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).