Re: [PATCH v3] contrib/nmbug: new script for sharing tags with a given prefix.
On Fri, 11 Nov 2011 10:08:15 -0500, David Bremner da...@tethera.net wrote: From: David Bremner brem...@debian.org The main idea is consider the notmuch database as analogous to the work-tree. A bare git repo is maintained in the users home directory, with a tree of the form tags/$message-id/$tag I pushed a slightly modified version of this to notmuch master. d ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH v3] contrib/nmbug: new script for sharing tags with a given prefix.
On Fri, 11 Nov 2011 15:26:28 -0800, Jameson Graef Rollins jroll...@finestructure.net wrote: On Fri, 11 Nov 2011 10:08:15 -0500, David Bremner da...@tethera.net wrote: The most important commands are commit xapian - git checkoutgit - xapian merge fetched git + git - xapian status find differences between xapian, git, and remote git. Hey, David. Just for clarification, the above seems a little inconsistent with the documentation included with the script, which implies that the most common commands, which are I believe meant to be the only ones that the user should routinely have to use, are commit, push, and pull. I got the impression that checkout and merge should only be needed if you're trying to recover a broken system. Hi Jamie; I think the commit message and the online help are aimed a different audience, so it is not crucial (or even desirable) that they be exactly the same. Perhaps it would be more clear to say that these are the non-trivial commands. The most commonly used commands could be retitled the minimal set of commands to use nmbug. My own workflow involves fetch, merge, and the occasional checkout. Your might or might not; in my case it has to do with the fact that I am syncing tags in several different ways. There are also some convenience wrappers around git commands. Isn't much of nmbug convenience wrappers around git commands? The distinction I'm trying to make here is between one-liners like fetch and slightly hairy things like commit, where I had to learn new things about git to implement the latter. It seems to me that the fact that nmbug is using git underneath should be almost completely abstracted away from the user. Well, in the sense that user should not normally have to use raw git commands, I agree. I don't really see any point in hiding the fact that it is using git e.g. in the documentation. It doesn't seem likely that nmbug will support more than one version control system without a complete rewrite. And of course the commit messages are supposed to tell how things work, so no point being coy there. d ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH v3] contrib/nmbug: new script for sharing tags with a given prefix.
On Fri, 11 Nov 2011 18:55:15 -0500, David Bremner da...@tethera.net wrote: I think the commit message and the online help are aimed a different audience, so it is not crucial (or even desirable) that they be exactly the same. Perhaps it would be more clear to say that these are the non-trivial commands. At this point I actually think they're probably exactly the same audience, aren't they? Isn't nmbug primarily aimed at notmuch developers that are reading patches sent to the list? The most commonly used commands could be retitled the minimal set of commands to use nmbug. My own workflow involves fetch, merge, and the occasional checkout. Your might or might not; in my case it has to do with the fact that I am syncing tags in several different ways. This is the sort of thing that I'm finding confusing. Is this your work flow because you are the primary developer and are therefore frequently working under the hood, or because this is the prescribed procedure? The tag sharing process that nmbug is using is complicated and subtle enough that you should make it very clear what the proper procedure is, and what are the under the hood commands that one should never really have to use. I've been following pretty closely and I'm still kind of confused. I'm sure that others coming to it now because they're seeing this posting to the list might share that confusion. Maybe it would help if you could follow up with a good how-to that describes how someone could start using nmbug with a nicely defined prescribed procedure. jamie. pgpkPRU29p9Gk.pgp Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH v3] contrib/nmbug: new script for sharing tags with a given prefix.
On Fri, 11 Nov 2011 18:43:38 -0800, Jameson Graef Rollins jroll...@finestructure.net wrote: On Fri, 11 Nov 2011 18:55:15 -0500, David Bremner da...@tethera.net wrote: At this point I actually think they're probably exactly the same audience, aren't they? Isn't nmbug primarily aimed at notmuch developers that are reading patches sent to the list? Well, same people, different roles. I maintain that the purpose of commit messages and online help is different. Commit messages are intended to help understand the implementation, help message how to use it. My own workflow involves fetch, merge, and the occasional checkout. Your might or might not; in my case it has to do with the fact that I am syncing tags in several different ways. This is the sort of thing that I'm finding confusing. Is this your work flow because you are the primary developer and are therefore frequently working under the hood, or because this is the prescribed procedure? From my point of view the analogy with git is fairly precise. Some people prefer the convenience of pull, some people prefer to sanity check the fetched changes (in the case of nmbug, using status) before merging. I guess people only using notmuch on one primary machine are less likely need checkout. The error message from nmbug pull explains when you might want checkout. Maybe it would help if you could follow up with a good how-to that describes how someone could start using nmbug with a nicely defined prescribed procedure. I have rewritten the page http://notmuchmail/nmbug to compare the short and simple workflow with expanded and fussy workflow. d ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
