From: Catalin Marinas <catalin.marinas@gmail.com>
To: Bryan Larsen <bryanlarsen@yahoo.com>
Cc: bryan.larsen@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH] stgit: allow spaces in filenames
Date: Wed, 13 Jul 2005 11:17:44 +0100 [thread overview]
Message-ID: <tnxll4bdn7b.fsf@arm.com> (raw)
In-Reply-To: <20050713083805.18461.87079.sendpatchset@bryan-larsens-ibook-g4.local> (Bryan Larsen's message of "Wed, 13 Jul 2005 04:38:11 -0400")
Bryan Larsen <bryanlarsen@yahoo.com> wrote:
> The current version of stgit does not allow whitespace in filenames.
> This patch fixes that. It also speeds up operations on large
> filesets considerably.
Thanks, I will apply it but I have a few comments below:
> +# __run: runs cmd using spawnvp.
> +#
> +# The shell is avoided so it won't mess up our arguments.
> +# If args is very large, the command is run multiple times;
> +# args is split xargs style: cmd is passed on each invocation.
> +# Unlike xargs, returns immediately if any non-zero return code
> +# is received.
> +#
> +def __run(cmd, args=None):
I would prefer to add this as Python function documentation, i.e. with
"""...""" in the function body.
An additional thing, can you please convert all the tabs to spaces?
That's a better convention for a language like Python where you
delimit blocks by indentation.
> @@ -114,14 +132,16 @@ def __tree_status(files = [], tree_id =
> # unknown files
> if unknown:
> exclude_file = os.path.join(base_dir, 'exclude')
> - extra_exclude = ''
> + extra_exclude = []
> if os.path.exists(exclude_file):
> - extra_exclude += ' --exclude-from=%s' % exclude_file
> - fout = os.popen('git-ls-files --others'
> - ' --exclude="*.[ao]" --exclude=".*"'
> - ' --exclude=TAGS --exclude=tags --exclude="*~"'
> - ' --exclude="#*"' + extra_exclude, 'r')
> + extra_exclude.append('--exclude-from=%s' % exclude_file)
> + fin, fout = os.popen2(['git-ls-files', '--others',
> + '--exclude=*.[ao]', '--exclude=.*'
> + '--exclude=TAGS', '--exclude=tags', '--exclude=*~',
> + '--exclude=#*'] + extra_exclude)
> cache_files += [('?', line.strip()) for line in fout]
> + fin.close()
> + fout.close()
What's the reason for having 'fin' as well? It doesn't seem to be used
(this is found in other parts of the patch as well).
Something wrong happened to my git-ftp-push script. It looks like it
copied 'master' to stgit.git/ and not to stgit.git/refs/heads/. I
can't fix it until tonight. Before then, you could actually use wget
to pull the whole repository and just copy 'master' to
'refs/heads/master'. In the latest tree I created separate files for
each command.
I'm not sure whether the GIT guys are happy for us to use this mailing
list for StGIT. If the StGIT traffic increases, I will try to create a
separate mailing list (maybe using a site like sf.net).
--
Catalin
next prev parent reply other threads:[~2005-07-13 10:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 8:38 [PATCH] stgit: allow spaces in filenames Bryan Larsen
2005-07-13 8:38 ` [PATCH] stgit: new --message does not work Bryan Larsen
2005-07-13 10:17 ` Catalin Marinas [this message]
2005-07-13 18:17 ` [PATCH] stgit: allow spaces in filenames Bryan Larsen
2005-07-13 21:09 ` Jerry Seutter
2005-07-13 21:26 ` Catalin Marinas
2005-07-13 22:26 ` Junio C Hamano
2005-07-14 7:02 ` Catalin Marinas
2005-07-14 7:22 ` Bryan Larsen
2005-07-13 16:54 ` Matthias Urlichs
2005-07-13 19:51 ` Linus Torvalds
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=tnxll4bdn7b.fsf@arm.com \
--to=catalin.marinas@gmail.com \
--cc=bryan.larsen@gmail.com \
--cc=bryanlarsen@yahoo.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).