All of lore.kernel.org
 help / color / mirror / Atom feed
From: nn6eumtr <nn6eumtr@gmail.com>
To: Neal Kreitzinger <nkreitzinger@gmail.com>, git@vger.kernel.org
Subject: Re: How to deal with historic tar-balls
Date: Fri, 06 Jan 2012 20:10:57 -0500	[thread overview]
Message-ID: <4F079BA1.3060907@gmail.com> (raw)
In-Reply-To: <4F05C0E2.4050101@gmail.com>

Thanks for the response, there is lots of good information there.

One clarification - can you track renames in git? I tried using git mv 
but from the status output it looks like it deleted the old file  and 
added the new file. I was expecting it to record some sort of indicator 
of the name change, instead it looks like a short-cut for delete & add, 
the docs aren't clear if that is the case.

On 1/5/2012 10:25 AM, Neal Kreitzinger wrote:
...
> going to want to do appropriate clean up of the working tree in each
> iteration before committing. This is where you would review
> renames/removes with git-status before you git-add and git-commit. Also,
> if you are tracking permissions in git (the executable bit) then you
> will want to filter out any noise generated by frivolous permissions
> changes between the tarball contents.
...

  reply	other threads:[~2012-01-07  1:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-31 19:04 How to deal with historic tar-balls nn6eumtr
2012-01-01  0:27 ` Tomas Carnecky
2012-01-01 18:30   ` Philip Oakley
2012-01-01 20:54     ` Philip Oakley
2012-01-02 10:07     ` Philip Oakley
2012-01-02 18:26       ` Dirk Süsserott
2012-01-04 20:04         ` Philip Oakley
2012-01-01 19:04   ` Dirk Süsserott
2012-01-05 15:25 ` Neal Kreitzinger
2012-01-07  1:10   ` nn6eumtr [this message]
2012-01-07  1:50     ` Thomas Rast
2012-01-07 19:18     ` Neal Kreitzinger

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=4F079BA1.3060907@gmail.com \
    --to=nn6eumtr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nkreitzinger@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.