Looks good to me :).
Cheers,
Trevor
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: appli
On Sat, Jan 03, 2015 at 07:12:13PM +0200, Tomi Ollila wrote:
> … so this makes me wonder whether there is actually anyone needing
> rst2man there…
Requiring Sphinx >= 1.0 (2010-07-23 [1]) to build man pages is fine
with me.
Cheers,
Trevor
[1]: https://pypi.python.org/pypi/Sphinx/1.0
--
This em
On Sat, Jan 03, 2015 at 07:12:13PM +0200, Tomi Ollila wrote:
> ? so this makes me wonder whether there is actually anyone needing
> rst2man there?
Requiring Sphinx >= 1.0 (2010-07-23 [1]) to build man pages is fine
with me.
Cheers,
Trevor
[1]: https://pypi.python.org/pypi/Sphinx/1.0
--
This em
On Sat, Jan 03, 2015 at 04:49:27PM +0100, David Bremner wrote:
> At the risk of bike-shedding, rewrite the configure check to be more
> "obvious". This is pretty subjective, but in particular I'm not a
> big fan of resetting RST2MAN at the bottom of every iteration of the
> for loop. Also conform
On Sat, Jan 03, 2015 at 04:49:27PM +0100, David Bremner wrote:
> At the risk of bike-shedding, rewrite the configure check to be more
> "obvious". This is pretty subjective, but in particular I'm not a
> big fan of resetting RST2MAN at the bottom of every iteration of the
> for loop. Also conform
On Sat, Nov 29, 2014 at 12:09:17PM -0800, W. Trevor King wrote:
> On Sat, Nov 29, 2014 at 10:40:01AM +0100, Michal Sojka wrote:
> > On Út, říj 28 2014, W. Trevor King wrote:
> > > +_spawn(
> > > +args=['git', 'in
On Sat, Nov 29, 2014 at 12:09:17PM -0800, W. Trevor King wrote:
> On Sat, Nov 29, 2014 at 10:40:01AM +0100, Michal Sojka wrote:
> > On ?t, ??j 28 2014, W. Trevor King wrote:
> > > +_spawn(
> > > +args=['git', 'in
On Sat, Nov 29, 2014 at 10:40:01AM +0100, Michal Sojka wrote:
> On Út, říj 28 2014, W. Trevor King wrote:
> > +_spawn(
> > +args=['git', 'init', '--separate-git-dir', NMBGIT, workdir],
> > +wait=True)
> >
On Sat, Nov 29, 2014 at 10:40:01AM +0100, Michal Sojka wrote:
> On ?t, ??j 28 2014, W. Trevor King wrote:
> > +_spawn(
> > +args=['git', 'init', '--separate-git-dir', NMBGIT, workdir],
> > +wait=True)
> >
Hello everyone :),
I like Git, so when folks suggest storing things in Git, I'm usually
excited ;). Eric Wong has been working on some tools to store email
in a Git repository, and his client-side code is ssoma [1]. I wanted
a bit more metadata than the stock ssoma-mda [2], and ended up just
wri
Hello everyone :),
I like Git, so when folks suggest storing things in Git, I'm usually
excited ;). Eric Wong has been working on some tools to store email
in a Git repository, and his client-side code is ssoma [1]. I wanted
a bit more metadata than the stock ssoma-mda [2], and ended up just
wri
On Fri, Oct 31, 2014 at 02:04:50PM -0400, Jesse Rosenthal wrote:
> W. Trevor King writes:
> > On Fri, Oct 31, 2014 at 01:33:25PM -0400, Jesse Rosenthal wrote:
> >> We instead initalize the dictionary using the dict comprehension
> >> and then update it with the values fr
On Fri, Oct 31, 2014 at 02:04:50PM -0400, Jesse Rosenthal wrote:
> W. Trevor King writes:
> > On Fri, Oct 31, 2014 at 01:33:25PM -0400, Jesse Rosenthal wrote:
> >> We instead initalize the dictionary using the dict comprehension
> >> and then update it with the values fr
On Fri, Oct 31, 2014 at 01:33:25PM -0400, Jesse Rosenthal wrote:
> We instead initalize the dictionary using the dict comprehension and
> then update it with the values from the tree. This will work with
> both python2 and python3.
Dict comprehensions are new in 2.7 [1,2], so this drops support fo
On Fri, Oct 31, 2014 at 01:33:25PM -0400, Jesse Rosenthal wrote:
> We instead initalize the dictionary using the dict comprehension and
> then update it with the values from the tree. This will work with
> both python2 and python3.
Dict comprehensions are new in 2.7 [1,2], so this drops support fo
For folks that want to start versioning a new tag-space, instead of
cloning one that someone else has already started.
The empty-blob hash-object call avoids errors like:
$ nmbug commit
error: invalid object 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 for
'tags/...'
fatal: git-write-tre
For folks that want to start versioning a new tag-space, instead of
cloning one that someone else has already started.
The empty-blob hash-object call avoids errors like:
$ nmbug commit
error: invalid object 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 for
'tags/...'
fatal: git-write-tre
On Sat, Oct 11, 2014 at 09:02:20AM +0200, David Bremner wrote:
> W. Trevor King writes:
> > On Sat, Oct 11, 2014 at 06:53:11AM +0200, David Bremner wrote:
> >> W. Trevor King writes:
> >> > but I expect that closing stdin is more portable than the
> >> &g
On Sat, Oct 11, 2014 at 09:02:20AM +0200, David Bremner wrote:
> W. Trevor King writes:
> > On Sat, Oct 11, 2014 at 06:53:11AM +0200, David Bremner wrote:
> >> W. Trevor King writes:
> >> > but I expect that closing stdin is more portable than the
> >> &g
On Sat, Oct 11, 2014 at 06:53:11AM +0200, David Bremner wrote:
> W. Trevor King writes:
> > but I expect that closing stdin is more portable than the /dev/null
> > path.
>
> /dev/null is part of POSIX
Maybe folks want to use nmbug on Windows or some other crazy non-POSIX
On Sat, Oct 11, 2014 at 06:53:11AM +0200, David Bremner wrote:
> W. Trevor King writes:
> > but I expect that closing stdin is more portable than the /dev/null
> > path.
>
> /dev/null is part of POSIX
Maybe folks want to use nmbug on Windows or some other crazy non-POSIX
For folks that want to start versioning a new tag-space, instead of
cloning one that someone else has already started.
The empty-blob hash-object call avoids errors like:
$ nmbug commit
error: invalid object 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 for
'tags/...'
fatal: git-write-tre
For folks that want to start versioning a new tag-space, instead of
cloning one that someone else has already started.
The empty-blob hash-object call avoids errors like:
$ nmbug commit
error: invalid object 100644 e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 for
'tags/...'
fatal: git-write-tre
For more details, see the commit message for 7f2cb3be (nmbug:
Translate to Python, 2014-10-03). I realized while writing this that
the 7f2cb3be commit message has:
* 'nmbug log' now execs 'git log', as there's no need to keep the
Python process around once we've launched Git there.
But we
For more details, see the commit message for 7f2cb3be (nmbug:
Translate to Python, 2014-10-03). I realized while writing this that
the 7f2cb3be commit message has:
* 'nmbug log' now execs 'git log', as there's no need to keep the
Python process around once we've launched Git there.
But we
On Tue, Oct 07, 2014 at 08:30:34AM +0200, David Bremner wrote:
> W. Trevor King writes:
> > This is mostly culled from the commit message for 7f2cb3be (nmbug:
> > Translate to Python, 2014-10-03). I realized while writing it
> > that the 7f2cb3be commit message has:
>
>
On Tue, Oct 07, 2014 at 08:30:34AM +0200, David Bremner wrote:
> W. Trevor King writes:
> > This is mostly culled from the commit message for 7f2cb3be (nmbug:
> > Translate to Python, 2014-10-03). I realized while writing it
> > that the 7f2cb3be commit message has:
>
>
This is mostly culled from the commit message for 7f2cb3be (nmbug:
Translate to Python, 2014-10-03). I realized while writing it that
the 7f2cb3be commit message has:
* 'nmbug log' now execs 'git log', as there's no need to keep the
Python process around once we've launched Git there.
But
This is mostly culled from the commit message for 7f2cb3be (nmbug:
Translate to Python, 2014-10-03). I realized while writing it that
the 7f2cb3be commit message has:
* 'nmbug log' now execs 'git log', as there's no need to keep the
Python process around once we've launched Git there.
But
push local nmbug git state to remote repo
-
-=item B [remote] [branch]
-
-pull (merge) remote repo changes to notmuch. B is equivalent to
-B followed by B. The default remote is C, and
-the default branch is C.
-
-=back
-
-=head2 Other Useful Commands
-
-=over 8
-
-=item B repository
-
-Create
h at David's request.
[1]: id:d44bb6ad59ee0a30ac4a8d2e9fe50e3b98d1c408.1411572592.git.wk...@tremily.us
http://thread.gmane.org/gmane.mail.notmuch.general/19108
W. Trevor King (2):
nmbug: Translate to Python
nmbug: Add a 'help' command for folks who don&
The 'if args.func == help' block at the end avoids:
AttributeError: 'functools.partial' object has no attribute '__code__'
---
devel/nmbug/nmbug | 31 ++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/devel/nmbug/nmbug b/devel/nmbug/nmbug
index 9402
The 'if args.func == help' block at the end avoids:
AttributeError: 'functools.partial' object has no attribute '__code__'
---
devel/nmbug/nmbug | 31 ++-
1 file changed, 30 insertions(+), 1 deletion(-)
diff --git a/devel/nmbug/nmbug b/devel/nmbug/nmbug
index 9402
push local nmbug git state to remote repo
-
-=item B [remote] [branch]
-
-pull (merge) remote repo changes to notmuch. B is equivalent to
-B followed by B. The default remote is C, and
-the default branch is C.
-
-=back
-
-=head2 Other Useful Commands
-
-=over 8
-
-=item B repository
-
-Create
h at David's request.
[1]: id:d44bb6ad59ee0a30ac4a8d2e9fe50e3b98d1c408.1411572592.git.wking at
tremily.us
http://thread.gmane.org/gmane.mail.notmuch.general/19108
W. Trevor King (2):
nmbug: Translate to Python
nmbug: Add a 'help' command for folks who don&
On Thu, Oct 02, 2014 at 04:39:41PM -0400, Austin Clements wrote:
> On Thu, 02 Oct 2014, W. Trevor King wrote:
> > On Thu, Oct 02, 2014 at 03:19:08PM -0400, Austin Clements wrote:
> >> This patch simplifies notmuch_database_close to explicitly abort
> >> any outstandin
On Thu, Oct 02, 2014 at 04:39:41PM -0400, Austin Clements wrote:
> On Thu, 02 Oct 2014, W. Trevor King wrote:
> > On Thu, Oct 02, 2014 at 03:19:08PM -0400, Austin Clements wrote:
> >> This patch simplifies notmuch_database_close to explicitly abort
> >> any outstandin
On Thu, Oct 02, 2014 at 03:19:08PM -0400, Austin Clements wrote:
> This patch simplifies notmuch_database_close to explicitly abort any
> outstanding transaction and then just call Database::close. This
> works for both read-only and read/write databases, takes care of
> committing changes, unifie
On Thu, Oct 02, 2014 at 03:19:08PM -0400, Austin Clements wrote:
> This patch simplifies notmuch_database_close to explicitly abort any
> outstanding transaction and then just call Database::close. This
> works for both read-only and read/write databases, takes care of
> committing changes, unifie
On Wed, Sep 24, 2014 at 05:32:50PM -0400, Austin Clements wrote:
> + * If the caller is currently in an atomic section (there was a
> + * notmuch_database_begin_atomic without a matching
> + * notmuch_database_end_atomic), this will abort the atomic section,
> + * discarding any modifications made
On Wed, Sep 24, 2014 at 05:32:50PM -0400, Austin Clements wrote:
> + * If the caller is currently in an atomic section (there was a
> + * notmuch_database_begin_atomic without a matching
> + * notmuch_database_end_atomic), this will abort the atomic section,
> + * discarding any modifications made
On Wed, Sep 24, 2014 at 05:20:23PM -0400, Austin Clements wrote:
> diff --git a/lib/notmuch.h b/lib/notmuch.h
> index fe2340b..5c40c67 100644
> --- a/lib/notmuch.h
> +++ b/lib/notmuch.h
> @@ -292,6 +292,11 @@ notmuch_database_open (const char *path,
> * notmuch_database_close can be called multip
On Wed, Sep 24, 2014 at 05:20:23PM -0400, Austin Clements wrote:
> diff --git a/lib/notmuch.h b/lib/notmuch.h
> index fe2340b..5c40c67 100644
> --- a/lib/notmuch.h
> +++ b/lib/notmuch.h
> @@ -292,6 +292,11 @@ notmuch_database_open (const char *path,
> * notmuch_database_close can be called multip
On Wed, Sep 24, 2014 at 10:13:31PM +0200, David Bremner wrote:
> W. Trevor King writes:
> I think it would be better to write our own, not because of licensing
> issues, but because the user of the notmuch API won't know what a xapian
> commit is.
Between version control and
On Wed, Sep 24, 2014 at 10:13:31PM +0200, David Bremner wrote:
> W. Trevor King writes:
> I think it would be better to write our own, not because of licensing
> issues, but because the user of the notmuch API won't know what a xapian
> commit is.
Between version control and
On Wed, Sep 24, 2014 at 09:25:20PM +0200, David Bremner wrote:
> I think the fact that you have to close the notmuch database (when
> not using begin/end atomic) to get a commit is surprising for many
> people, so it would be nice to make that clearer somehow.
It looks like Xapian is GPLv2+, so we
On Wed, Sep 24, 2014 at 09:25:20PM +0200, David Bremner wrote:
> I think the fact that you have to close the notmuch database (when
> not using begin/end atomic) to get a commit is surprising for many
> people, so it would be nice to make that clearer somehow.
It looks like Xapian is GPLv2+, so we
On Wed, Sep 24, 2014 at 08:09:27PM +0200, David Bremner wrote:
> W. Trevor King writes:
> > Ah, I thought the implicit flush/commit was just in our code.
> > Since it's also in the underlying Xapian close, then this patch
> > looks pretty good to me. I'd mention Xap
On Wed, Sep 24, 2014 at 08:09:27PM +0200, David Bremner wrote:
> W. Trevor King writes:
> > Ah, I thought the implicit flush/commit was just in our code.
> > Since it's also in the underlying Xapian close, then this patch
> > looks pretty good to me. I'd mention Xap
C.
-
-=back
-
-=head2 Other Useful Commands
-
-=over 8
-
-=item B repository
-
-Create a local nmbug repository from a remote source. This wraps
-C, adding some options to avoid creating a working tree
-while preserving remote-tracking branches and upstreams.
-
-=item B
-
-Update the notmuch dat
nch is C.
-
-=back
-
-=head2 Other Useful Commands
-
-=over 8
-
-=item B repository
-
-Create a local nmbug repository from a remote source. This wraps
-C, adding some options to avoid creating a working tree
-while preserving remote-tracking branches and upstreams.
-
-=item B
-
-Update the notmu
On Mon, Sep 22, 2014 at 06:50:50PM +, Austin Clements wrote:
> Quoth W. Trevor King on Sep 22 at 9:59 am:
> > On Mon, Sep 22, 2014 at 11:43:35AM -0400, Austin Clements wrote:
> > > This patch simplifies notmuch_database_close to just call
> > > Database::close. Th
On Mon, Sep 22, 2014 at 06:50:50PM +, Austin Clements wrote:
> Quoth W. Trevor King on Sep 22 at 9:59 am:
> > On Mon, Sep 22, 2014 at 11:43:35AM -0400, Austin Clements wrote:
> > > This patch simplifies notmuch_database_close to just call
> > > Database::close. Th
On Mon, Sep 22, 2014 at 10:19:35AM -0700, W. Trevor King wrote:
> I like nmbug's distributed tag maintenance, but not everyone has
> notmuch/nmbug installed locally (yet ;). However, everyone that I
> know does have a browser and a mail client. They can submit
> messages with
On Mon, Sep 22, 2014 at 10:19:35AM -0700, W. Trevor King wrote:
> I like nmbug's distributed tag maintenance, but not everyone has
> notmuch/nmbug installed locally (yet ;). However, everyone that I
> know does have a browser and a mail client. They can submit
> messages with
I like nmbug's distributed tag maintenance, but not everyone has
notmuch/nmbug installed locally (yet ;). However, everyone that I
know does have a browser and a mail client. They can submit messages
with their mail client already, but we've been missing a way for them
to help tag messages. Nmhi
I like nmbug's distributed tag maintenance, but not everyone has
notmuch/nmbug installed locally (yet ;). However, everyone that I
know does have a browser and a mail client. They can submit messages
with their mail client already, but we've been missing a way for them
to help tag messages. Nmhi
On Mon, Sep 22, 2014 at 11:43:35AM -0400, Austin Clements wrote:
> This patch simplifies notmuch_database_close to just call
> Database::close. This works for both read-only and read/write
> databases, takes care of committing changes, unifies the exception
> handling path, and codifies aborting o
On Mon, Sep 22, 2014 at 11:43:35AM -0400, Austin Clements wrote:
> This patch simplifies notmuch_database_close to just call
> Database::close. This works for both read-only and read/write
> databases, takes care of committing changes, unifies the exception
> handling path, and codifies aborting o
On Mon, Sep 15, 2014 at 08:09:11PM +0200, David Bremner wrote:
> W. Trevor King writes:
> > Give it a spin to kick the tires, and reply to the v4 patch saying
> > that none of the pieces fell off while you were kicking it ;).
> > Basically, it's just waiting for review
On Mon, Sep 15, 2014 at 08:09:11PM +0200, David Bremner wrote:
> W. Trevor King writes:
> > Give it a spin to kick the tires, and reply to the v4 patch saying
> > that none of the pieces fell off while you were kicking it ;).
> > Basically, it's just waiting for review
On Mon, Sep 15, 2014 at 05:32:59PM +0100, David Edmondson wrote:
> On Mon, Sep 15 2014, W. Trevor King wrote:
> > On Mon, Sep 15, 2014 at 05:13:50PM +0100, David Edmondson wrote:
> >> On Sun, Jul 06 2014, W. Trevor King wrote:
> >> > For folks that want to start versi
On Mon, Sep 15, 2014 at 05:32:59PM +0100, David Edmondson wrote:
> On Mon, Sep 15 2014, W. Trevor King wrote:
> > On Mon, Sep 15, 2014 at 05:13:50PM +0100, David Edmondson wrote:
> >> On Sun, Jul 06 2014, W. Trevor King wrote:
> >> > For folks that want to start versi
On Mon, Sep 15, 2014 at 05:13:50PM +0100, David Edmondson wrote:
> On Sun, Jul 06 2014, W. Trevor King wrote:
> > For folks that want to start versioning a new tag-space, instead
> > of cloning one that someone else has already started.
>
> I tried this patch, and it (app
On Mon, Sep 15, 2014 at 05:13:50PM +0100, David Edmondson wrote:
> On Sun, Jul 06 2014, W. Trevor King wrote:
> > For folks that want to start versioning a new tag-space, instead
> > of cloning one that someone else has already started.
>
> I tried this patch, and it (app
On Mon, Sep 15, 2014 at 03:26:26PM +0100, David Edmondson wrote:
> On Mon, Sep 15 2014, W. Trevor King wrote:
> > Does nmbug not do this for you? This is exactly what it was designed
> > to do (sync tags).
>
> Perhaps. Is anyone using it for personal tag sync?
I will once
On Mon, Sep 15, 2014 at 03:26:26PM +0100, David Edmondson wrote:
> On Mon, Sep 15 2014, W. Trevor King wrote:
> > Does nmbug not do this for you? This is exactly what it was designed
> > to do (sync tags).
>
> Perhaps. Is anyone using it for personal tag sync?
I will once
On Mon, Sep 15, 2014 at 02:49:16PM +0100, David Edmondson wrote:
> On Thu, May 20 2010, David Edmondson wrote:
> (Wow, was it really more than four years ago?)
>
> > What's the current state of the art in merging tags from multiple
> > machines?
> >
> > In my own case the contents of the mail stor
On Mon, Sep 15, 2014 at 02:49:16PM +0100, David Edmondson wrote:
> On Thu, May 20 2010, David Edmondson wrote:
> (Wow, was it really more than four years ago?)
>
> > What's the current state of the art in merging tags from multiple
> > machines?
> >
> > In my own case the contents of the mail stor
e] [branch]
-
-pull (merge) remote repo changes to notmuch. B is equivalent to
-B followed by B. The default remote is C, and
-the default branch is C.
-
-=back
-
-=head2 Other Useful Commands
-
-=over 8
-
-=item B repository
-
-Create a local nmbug repository from a remote source. This wraps
-C,
to remote repo
-
-=item B [remote] [branch]
-
-pull (merge) remote repo changes to notmuch. B is equivalent to
-B followed by B. The default remote is C, and
-the default branch is C.
-
-=back
-
-=head2 Other Useful Commands
-
-=over 8
-
-=item B repository
-
-Create a local nmbug repository from a rem
On Tue, Aug 05, 2014 at 10:24:10PM -0300, David Bremner wrote:
> I have a local commit that deletes a couple tags; when I attempt to
> merge I get complaints about local changes to files.
>
> error: Your local changes to the following files would be overwritten by
> merge:
> tags/1406859003
On Tue, Aug 05, 2014 at 10:24:10PM -0300, David Bremner wrote:
> I have a local commit that deletes a couple tags; when I attempt to
> merge I get complaints about local changes to files.
>
> error: Your local changes to the following files would be overwritten by
> merge:
> tags/1406859003
On Tue, Aug 05, 2014 at 10:16:10PM -0300, David Bremner wrote:
> David Bremner writes:
> > I did notice that merging was noticably noisier than I remembered.
>
> rejected pushes also seem noisier than before; I'm not sure the
> python backtrace adds anything here.
>
> To nm...@nmbug.tethera.net
On Tue, Aug 05, 2014 at 10:16:10PM -0300, David Bremner wrote:
> David Bremner writes:
> > I did notice that merging was noticably noisier than I remembered.
>
> rejected pushes also seem noisier than before; I'm not sure the
> python backtrace adds anything here.
>
> To nmbug at nmbug.tethera.
On Mon, Aug 04, 2014 at 09:14:46PM -0300, David Bremner wrote:
> W. Trevor King writes:
> > * Commands are no longer split into "most common", "other useful",
> > and "less common" sets. If we need something like this, I'd
> > pref
On Mon, Aug 04, 2014 at 09:14:46PM -0300, David Bremner wrote:
> W. Trevor King writes:
> > * Commands are no longer split into "most common", "other useful",
> > and "less common" sets. If we need something like this, I'd
> > pref
I should also import print_function and unicode_literals from
__future__ for Python 2.x compatibility, since I use print() once and
never use bytes. I hadn't turned up any problems with 2.x without the
__future__ imports, but it's nice to be explicit ;).
Cheers,
Trevor
--
This email may be sign
I should also import print_function and unicode_literals from
__future__ for Python 2.x compatibility, since I use print() once and
never use bytes. I hadn't turned up any problems with 2.x without the
__future__ imports, but it's nice to be explicit ;).
Cheers,
Trevor
--
This email may be sign
On Sun, Jul 20, 2014 at 03:59:49PM -0700, W. Trevor King wrote:
> +def pull(repository=None, refspecs=None):
> +"""
> +Pull (merge) remote repository changes to notmuch.
> +
> +'pull' is equivalent to 'fetch' followed by 'merge&
On Sun, Jul 20, 2014 at 03:59:49PM -0700, W. Trevor King wrote:
> +def pull(repository=None, refspecs=None):
> +"""
> +Pull (merge) remote repository changes to notmuch.
> +
> +'pull' is equivalent to 'fetch' followed by 'merge&
On Sun, Jul 20, 2014 at 03:59:49PM -0700, W. Trevor King wrote:
> Most of the user-facing interface is the same, but there are a few
> changes, where reproducing the original interface was too difficult
> or I saw a change to make the underlying Git UI accessible:
It's not listed
On Sun, Jul 20, 2014 at 03:59:49PM -0700, W. Trevor King wrote:
> Most of the user-facing interface is the same, but there are a few
> changes, where reproducing the original interface was too difficult
> or I saw a change to make the underlying Git UI accessible:
It's not listed
This allows us to capture stdout and stderr separately, and do other
explicit subprocess manipulation without resorting to external
packages. It should be compatible with Python 2.6 and later
(including the 3.x series), although with 2.6 you'll need the external
argparse package.
Most of the user
This allows us to capture stdout and stderr separately, and do other
explicit subprocess manipulation without resorting to external
packages. It should be compatible with Python 2.6 and later
(including the 3.x series), although with 2.6 you'll need the external
argparse package.
Most of the user
This allows us to capture stdout and stderr separately, and do other
explicit subprocess manipulation without resorting to external
packages. It should be compatible with Python 2.6 and later
(including the 3.x series), although with 2.6 you'll need the external
argparse package.
Most of the user
This allows us to capture stdout and stderr separately, and do other
explicit subprocess manipulation without resorting to external
packages. It should be compatible with Python 2.6 and later
(including the 3.x series), although with 2.6 you'll need the external
argparse package.
Most of the user
This allows us to capture stdout and stderr separately, and do other
explicit subprocess manipulation without resorting to external
packages. It should be compatible with Python 2.6 and later
(including the 3.x series), although with 2.6 you'll need the external
argparse package.
Most of the user
This allows us to capture stdout and stderr separately, and do other
explicit subprocess manipulation without resorting to external
packages. It should be compatible with Python 2.6 and later
(including the 3.x series), although with 2.6 you'll need the external
argparse package.
Most of the user
On Thu, Jul 17, 2014 at 06:28:55AM -0300, David Bremner wrote:
> W. Trevor King writes:
> > On Wed, Jul 16, 2014 at 07:36:10PM -0300, David Bremner wrote:
> >> W. Trevor King writes:
> >> > If we don't have an upstream, there is nothing to merge, so
> >>
On Thu, Jul 17, 2014 at 06:28:55AM -0300, David Bremner wrote:
> W. Trevor King writes:
> > On Wed, Jul 16, 2014 at 07:36:10PM -0300, David Bremner wrote:
> >> W. Trevor King writes:
> >> > If we don't have an upstream, there is nothing to merge, so
> >>
On Wed, Jul 16, 2014 at 07:36:10PM -0300, David Bremner wrote:
> W. Trevor King writes:
> > If we don't have an upstream, there is nothing to merge, so
> > nothing is unmerged. This avoids errors like:
>
> pushed this one patch.
Without the stderr-catching of somethin
On Wed, Jul 16, 2014 at 07:36:10PM -0300, David Bremner wrote:
> W. Trevor King writes:
> > If we don't have an upstream, there is nothing to merge, so
> > nothing is unmerged. This avoids errors like:
>
> pushed this one patch.
Without the stderr-catching of somethin
On Tue, Jul 15, 2014 at 08:49:58PM -0300, David Bremner wrote:
> "W. Trevor King" writes:
>
> > + if ($dir eq '-2|') {
> > +$dir = '-|';
> > + }
> > +
>
> I think I'd prefer an extra flag, rather than making new synt
On Tue, Jul 15, 2014 at 08:49:58PM -0300, David Bremner wrote:
> "W. Trevor King" writes:
>
> > + if ($dir eq '-2|') {
> > +$dir = '-|';
> > + }
> > +
>
> I think I'd prefer an extra flag, rather than making new synt
On Tue, Jul 15, 2014 at 08:54:28PM -0300, David Bremner wrote:
> "W. Trevor King" writes:
>
> > +sub do_init {
> > + my $tempwork = tempdir ('/tmp/nmbug-init.XX', CLEANUP => 1);
> > + system ('git', 'init', '--separa
On Tue, Jul 15, 2014 at 08:54:28PM -0300, David Bremner wrote:
> "W. Trevor King" writes:
>
> > +sub do_init {
> > + my $tempwork = tempdir ('/tmp/nmbug-init.XX', CLEANUP => 1);
> > + system ('git', 'init', '--separa
On Tue, Jul 15, 2014 at 08:44:53PM -0300, David Bremner wrote:
> W. Trevor King writes:
> > - my $fetch_head = git ('rev-parse', $commit);
> > + my ($fetch_head, $status) = git_with_status ('rev-parse', $commit);
> > + if ($status) {
> > +retu
On Tue, Jul 15, 2014 at 08:44:53PM -0300, David Bremner wrote:
> W. Trevor King writes:
> > - my $fetch_head = git ('rev-parse', $commit);
> > + my ($fetch_head, $status) = git_with_status ('rev-parse', $commit);
> > + if ($status) {
> > +retu
On Mon, Jul 14, 2014 at 06:51:22AM -0300, David Bremner wrote:
> W. Trevor King writes:
> > On Sun, Jul 13, 2014 at 09:30:56AM -0300, David Bremner wrote:
> >> I consider it a useful feature that it works without the user
> >> configuring a local branch. I agree
101 - 200 of 518 matches
Mail list logo
