From: Miles Bader <miles@gnu.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Christian Couder <chriscool@tuxfamily.org>,
git@vger.kernel.org
Subject: Re: [PATCH 2/3] commit: add function to unparse a commit and its parents
Date: Tue, 19 May 2009 16:02:25 +0900 [thread overview]
Message-ID: <buozld9o9ry.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <m3r5ylk347.fsf@localhost.localdomain> (Jakub Narebski's message of "Mon, 18 May 2009 23:35:45 -0700 (PDT)")
Jakub Narebski <jnareb@gmail.com> writes:
>> git push $there 04a8c^2:master
>
> First, I have always thought that you cannot push arbitrary SHA-1
> (arbitrary commits) in git; you can only push via refs. Isn't it true?
Hmm, you could try it...
[Pushing random commits has always worked for me though.]
-miles
--
The secret to creativity is knowing how to hide your sources.
--Albert Einstein
next prev parent reply other threads:[~2009-05-19 7:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090517153307.6403.73576.>
2009-05-17 15:36 ` [PATCH 1/3] bisect: rework some rev related functions to make them more reusable Christian Couder
2009-05-17 15:36 ` [PATCH 2/3] commit: add function to unparse a commit and its parents Christian Couder
2009-05-18 6:27 ` Junio C Hamano
2009-05-19 4:16 ` Christian Couder
2009-05-19 5:20 ` Junio C Hamano
2009-05-19 6:35 ` Jakub Narebski
2009-05-19 7:02 ` Miles Bader [this message]
2009-05-19 7:14 ` Junio C Hamano
2009-05-19 7:48 ` Jakub Narebski
2009-05-25 9:17 ` Johannes Sixt
2009-05-25 9:46 ` Johannes Schindelin
2009-05-27 5:12 ` Christian Couder
2009-05-17 15:36 ` [PATCH 3/3] bisect: check ancestors without forking a "git rev-list" process Christian Couder
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=buozld9o9ry.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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.