[PATCH] FreeBSD backend

Dan Nicholson dbn.lists at gmail.com
Tue Nov 28 16:47:12 PST 2006


On 11/28/06, Joe Marcus Clarke <marcus at freebsd.org> wrote:
> On Tue, 2006-11-28 at 14:03 -0800, Dan Nicholson wrote:
> > On 11/28/06, David Zeuthen <david at fubar.dk> wrote:
> > >
> > > Ideally commit the shared code one unit at a time... and the full
> > > backend in one commit? You can do all the commits in your own tree and
> > > then generate patches (does anyone offhand know the magic git command to
> > > do that?) and send them to the list? Then we can test out the patches
> > > before you push all the changes..
> >
> > Something like
> >
> > git-format-patch -k --attach --stdout origin..master | git-send-email
> > --to hal at lists.freedesktop.org
> >
> > will create an mbox with a bunch of patches depending on what options
> > you pass to each command. I also mucked around with git-imap-send the
> > other day and it worked great once I had the relevant setting in
> > .git/config for imap. Read the man pages for git-format-patch and
> > git-send-email (and potentially git-imap-send).
>
> I did, but I cannot make this syntax work.  git-send-email expects file
> or directory names on the command line.  It does not like this data
> piped to it.  I can make this work on a patch-by-patch basis piping
> directly to sendmail, but this just seems too complicated.
>
> All I want to do is commit this work.  All of these hoops are just
> wearing me out.  I have all the glue code in mbox format at
> http://www.marcuscom.com/downloads/hal_git.mbox.  Can someone look that
> over, and let me know if I can push those changes?

Sorry about that. My experience had really been with git-imap-send
which accepts a pipe. It looks like the better way would be:

mkdir foo
git-format-patch --attach -o foo origin
git-send-email --to hal at lists.freedesktop.org foo/* (fill in the queries)

Although, I'm not having the best luck with git-send-email myself.

But, someone should be able to take your mbox file and run git-am with
it into their own tree. Also, the URL was wrong (.mobx vs. .mbox).
Here's the right one:

http://www.marcuscom.com/downloads/hal_git.mobx

The alternative would be to make your git repo accessible for someone
(David) to pull from.

--
Dan


More information about the hal mailing list