Hello, Na Sat, Jul 21, 2007 at 02:06:39AM +0200, lars <[EMAIL PROTECTED]> pisal(a): > 1) I do not know the directory structure of git. Is it really necessary to > scan > for the ".git" directory all the tree upwards? Or does the directory exist in > any directory of the working copy?
yes, it's necessary, it's just like darcs, there is a .git directory in the root of the repo > 2) The following lines are hard to understand for me: > + command = "git add %s; git commit -m '%s'; git push 2>/dev/null" \ > + % (shellescape(self.location), message) > > Does this mean, that we always have to 'add' the specific file before > committing? Is that always necessary? Do we have to implement it for > svn/cvs/darcs, too? yes, it's necessary. there are two choices: 1) git add file.c (even if it's already tracked by git) and git commit 2) git commit -a, but then everything will be committed, which is not what we want i know, it's quite confusing for somebody who never used git as in cvs/svn/darcs we use the 'add' command only for the first time, while in git we use it several times if we want to commit only specific files, not all the changes - VMiklos
pgpNm8pvchR8s.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Translate-pootle mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/translate-pootle
