git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Pazu <pazu@pazu.com.br>
Cc: Rogan Dawes <discard@dawes.za.net>, git@vger.kernel.org
Subject: Re: Ignoring local changes
Date: Fri, 15 Dec 2006 01:15:53 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.63.0612150114030.3635@wbgn013.biozentrum.uni-wuerzburg.de> (raw)
In-Reply-To: <9e7ab7380612141336p3b930047l3a4a76947239162f@mail.gmail.com>

Hi,

On Thu, 14 Dec 2006, Pazu wrote:

> 2006/12/14, Rogan Dawes <discard@dawes.za.net>:
> 
> > Why not remove it from the repo, then set .gitignore?
> > 
> > If it is generated code, or compiled code, it probably shouldn't be in
> > the repo in the first place . . . Simply correct that mistake, and you
> > are good to go.
> 
> Basically, because I don't want to mess with the upstream. I know, I
> can remove them only from my local branch, and never push the commit
> that removed the files, and that's what I'll probably do if there's no
> other way -- but it would be best if I could just ignore the files. It
> doesn't sound unreasonable, does it?

It is not unreasonable. But I could not find an easy way to do it with 
git. It should be easy to hack it into it, though.

Ciao,
Dscho

      parent reply	other threads:[~2006-12-15  0:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14 16:26 Ignoring local changes Pazu
2006-12-14 16:44 ` Andreas Ericsson
2006-12-14 16:55   ` Pazu
2006-12-14 21:27     ` Rogan Dawes
2006-12-14 21:36       ` Pazu
2006-12-14 21:56         ` Pazu
2006-12-15  0:15         ` Johannes Schindelin [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.63.0612150114030.3635@wbgn013.biozentrum.uni-wuerzburg.de \
    --to=johannes.schindelin@gmx.de \
    --cc=discard@dawes.za.net \
    --cc=git@vger.kernel.org \
    --cc=pazu@pazu.com.br \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).