gEDA-dev: gEDA-user: gEDA/gaf git repository now online

[Felipe Balbi]

Hi Peter,

On 6/21/07, Peter TB Brett <peter at peter-b.co.uk> wrote:
> > Please... do not let anyone but the maintainer (that would be you)
> > apply patches directly to the git repository. If do as I say, every
> > single patch should be sent to the mailing list, that would be the
> > only path in order to get them applied to git repository.
> >
> > After everybody agrees with the patch, you can save that message in a
> > different mailbox and run:
>
> That's fine when the maintainer has lots of time to work on patches, but
> doesn't work so well when they don't.  This has been discussed extensively on
> the -dev list and on IRC, and it was decided that the best bet was to operate
> with a centralised repository similarly to the way CVS works.  This is also a
> perfectly valid use model for git, and works very well for projects like
> X.org.

hmm... Ok...
whatever it's better for the project.

>
> > git-am <mailbox_with_patches> in the root directory of geda's git.
> >
> > and also... it's nice for you to create several branches... for
> > instance at linux-omap we use something like this:
> > linux-omap
>
> One of the main reasons for using git was to allow developers to use private
> branches more effectively.  Branching will be used within the main
> repository, but only for release branches or very major functionality changes
> (which might be better suited to a separate repo.

it's easier to just create a tag, like it's done in kernel.

whenever you want to release a version you can:

git-tag -s <name> <commit_id>  (or HEAD if you wanna tag the current
head revision)

and to make a tarball, you just:

git-archive --format=tar --prefix=geda-<version>/ <tag_name> | gzip >
geda-<version>.tar.gz

ex:
git-archive --format=tar --prefix=geda-2.2.2/ v2.2.2 | gzip > geda-2.2.2.tar.gz


you can also separate directories:

git-archive --format=tar --prefix=geda-docs/ v2.2.2:docs/ | gzip >
geda-docs-2.2.2.tar.gz


the only problem here is that bug fixes would come in later releases.


>
> If you'd like to discuss this further please do so on the -dev list.
>
> Regards,
>
> Peter
>
>
>
> --
> Fisher Society                              http://tinyurl.com/o39w2
> CU Small-Bore Club                          http://tinyurl.com/mwrc9
>
>       09f911029d74e35bd84156c5635688c0            peter-b.co.uk
>
>


-- 
Best Regards,

Felipe Balbi
felipebalbi at users.sourceforge.net