Re: CVS commit: pkgsrc/net/ocamlnet

Benny Siegert <[email protected]> writes:

> On Thu, Jul 19, 2012 at 2:58 PM, Greg Troxel <[email protected]> wrote:
>>
>>   most people don't maintain lots of unpushed state
>
> Why not? This would be (for me) one of the main advantages of using git.

When I work on pkgsrc, I rarely *want* to maintain much uncommitted state.
But maybe that's because it's hard.

>>   we don't have a lot of branches, perhaps none, and probably no
>>   branches without discussion
>
> Why not allow individual branches while somebody is working on, say,
> updating a particular port?

Sure, but the question is if they belong on the public server, or if
that's noise.

>> After you do all that, I don't see what we gain (other than leaving
>> sourceforge).
>
> The ability to do sensible local committing before pushing back your
> changes sounds compelling to me.

True, that does matter.  But much less in wip than other places.
It is nice that git lets you review the actual commit you are pushing.

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
pkgsrc-wip-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (NetBSD)

iEYEARECAAYFAlAIPfcACgkQ+vesoDJhHiUpbACgpmCQA8PBniQSTcrrkPjCFSZl
DmAAoIHOpUCDm8IlHIJchKSpiB6PHwez
=5qZv
-----END PGP SIGNATURE-----