threads / discuss / 6364

Re: Importing from tarballs; add, rm, update-index?

Subject: Re: Importing from tarballs; add, rm, update-index?

## tl;dr

3 messages between Jan 13, 2007 and Jan 15, 2007.

replies: 2people: 1as markdown or json

Horst H. von Brand· Jan 13, 2007, 22:04 UTC · lore
Shawn O. Pearce <spearce@spearce.org> wrote:
Show 11 quoted lines
> "Horst H. von Brand" <vonbrand@inf.utfsm.cl> wrote:
> > Please don't. It would add e.g. the .class and .o and all ~ files, and all
> > other junk you have lying around (test cases, test run output, ...). It
> > isn't /that/ much more work after creating a new file to record its
> > existence...
> 
>   echo \*.class >>.gitignore
>   echo \*.o >>.gitignore
>   git add .gitignore
> 
> doesn't work for some reason?

Because each time I build a bit of scaffolding, or have a new test output, or... I'd have to add them to .gitignore. I'd very much prefer tracking real contents and not junk.

-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                    Fono: +56 32 2654431
Universidad Tecnica Federico Santa Maria             +56 32 2654239
Casilla 110-V, Valparaiso, Chile               Fax:  +56 32 2797513
Horst H. von Brand· Jan 14, 2007, 23:49 UTC · lore
Shawn O. Pearce <spearce@spearce.org> wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > You mean, you _ignored_ the text "git commit -a" gives you? It really 
> > shows you the output of "git status", exactly so you know what you 
> > committed, and sometimes more importantly, what you didn't.
> Because I'm a moron and forgot what files I had created recently.
> Consequently I don't see them missing from the output of git commit.
> Consequently I think the commit is OK.  :-)

That can't be fixed by software... better get the habit of "git add"ing new files ASAP.

-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                    Fono: +56 32 2654431
Universidad Tecnica Federico Santa Maria             +56 32 2654239
Casilla 110-V, Valparaiso, Chile               Fax:  +56 32 2797513
Horst H. von Brand· Jan 15, 2007, 12:37 UTC · lore

Re: Commit signing

Shawn O. Pearce <spearce@spearce.org> wrote:
> Andy Parkins <andyparkins@gmail.com> wrote:
[...]
Show 7 quoted lines
> > The more I think about it, the more it could be a reasonable question.
> > In my own repository I can obviously create whatever commits i like,
> > claiming them to be from whomever I like just by altering a few config
> > settings.  If I put a few of those in my own repository and then
> > managed to persuade Junio to pull from me - wouldn't I have faked
> > commits from another developer? However, I wouldn't be able to fake a
> > gpg signature.
[...]
Show 9 quoted lines
> What I'm actually doing in one particular environment is checking
> the committer string against a database of known committer strings
> associated with the current UNIX uid.  My update hook[*1*] performs
> a `git log --pretty=raw $3 --not --all` query to determine any
> commits which are coming in as part of this push and which are not
> already referenced by an existing head or tag in this repository.
> For each of those the committer line *must* match one stored in
> the allowed-committers file for the current user, as these are
> brand new commits being introduced to the repository.

This only covers the "pure star" (centralized, CVS-like) topology: Each one only pushes their own changes, nobody collects changes from others and pushes the sum.

-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                    Fono: +56 32 2654431
Universidad Tecnica Federico Santa Maria             +56 32 2654239
Casilla 110-V, Valparaiso, Chile               Fax:  +56 32 2797513

← back to recent threads