Git development
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
To: martin f krafft <madduck@madduck.net>
Cc: git discussion list <git@vger.kernel.org>
Subject: Re: hiding a certain file from gitweb
Date: Tue, 21 Aug 2007 23:49:38 +0200	[thread overview]
Message-ID: <85veb8mubx.fsf@lola.goethe.zz> (raw)
In-Reply-To: <20070821190225.GA7133@piper.oerlikon.madduck.net> (martin f. krafft's message of "Tue\, 21 Aug 2007 21\:02\:25 +0200")

martin f krafft <madduck@madduck.net> writes:

> Dear list,
>
> one of my colleagues checked a file with thousands of email
> addresses into git and pushed the commit, so now the file is on
> gitweb. This was quite a while ago and we have over 500 commits and
> several branches between now and then.

This sounds like you would be ok with the file never having been
committed.  Use git-filter-branch for that.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-08-21 21:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21 19:02 hiding a certain file from gitweb martin f krafft
2007-08-21 21:49 ` David Kastrup [this message]
2007-08-21 22:40   ` martin f krafft

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=85veb8mubx.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=madduck@madduck.net \
    /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