git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: David Brown <git@davidb.org>
Cc: Git <git@vger.kernel.org>
Subject: Re: Referring a commit-id remote repo.
Date: Mon, 1 Oct 2007 11:25:13 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710011122500.28395@racer.site> (raw)
In-Reply-To: <20071001041635.GA22102@old.davidb.org>

Hi,

On Sun, 30 Sep 2007, David Brown wrote:

> The question I have: is there any way I can look at this particular 
> commit ID on the remote repo?  I couldn't come up with any way to get 
> git fetch to retrieve it.

Unless you have push access, no.  And this is very much by design.  For 
example, when somebody mistakenly pushed a secret (like what lines in the 
kernel infringe on M$ patents, if any) it should be possible to rebase (in 
a hurry), force a push, and have the safe feeling that nobody can fetch 
the secret any longer.

Ciao,
Dscho

  reply	other threads:[~2007-10-01 10:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01  4:16 Referring a commit-id remote repo David Brown
2007-10-01 10:25 ` Johannes Schindelin [this message]
2007-10-01 15:24   ` David Brown

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=Pine.LNX.4.64.0710011122500.28395@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@davidb.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).