Git development
 help / color / mirror / Atom feed
From: Bill Lear <rael@zopyra.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Shakthi Kannan <shakthimaan@gmail.com>, git@vger.kernel.org
Subject: Re: Query remote repository files, blobs
Date: Sat, 19 Dec 2009 07:31:08 -0600	[thread overview]
Message-ID: <19244.54684.250532.801766@lisa.zopyra.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0912191159280.4985@pacific.mpi-cbg.de>

On Saturday, December 19, 2009 at 12:02:02 (+0100) Johannes Schindelin writes:
>On Sat, 19 Dec 2009, Shakthi Kannan wrote:
>...
>> I am able to query for list of remote heads, and tags. I would like to
>> know if it is possible to query for information on remote files, or
>> blobs?
>
>This has been discussed a number of times, but we cannot allow that for 
>security reasons.  A blob might contain confidential information, in which 
>case the branch has to be rewritten and force-pushed.  However, that does 
>not make the blob go away, but makes it only unreachable.  Until the next 
>garbage collection kicks in, that is (which you typically cannot control).

Hmm, I thought this had been addressed by git in a different way (removing
confidential information).  A company will not be satisfied that its
proprietary information is "unreachable" in your software repository.
They want absolute assurance that the information is completely
removed.

Have I remembered wrongly --- is this still not possible with git?


Bill

  reply	other threads:[~2009-12-19 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19  7:45 Query remote repository files, blobs Shakthi Kannan
2009-12-19 11:02 ` Johannes Schindelin
2009-12-19 13:31   ` Bill Lear [this message]
2009-12-19 19:24     ` Shawn O. Pearce
2009-12-19 20:42       ` A Large Angry SCM
2009-12-19 20:50         ` 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=19244.54684.250532.801766@lisa.zopyra.com \
    --to=rael@zopyra.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=shakthimaan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox