Le lundi 28 avril 2008, à 11:47 -0400, Rodney Dawes a écrit :
On Sat, 2008-04-26 at 15:55 +0200, Vincent Untz wrote:
Hi,
I've asked for the creation of a git repository to host all fd.o specs
(will make things much easier). I think it'd make sense to send commit
notifications to this
On Mon, 2008-04-28 at 11:47 -0400, Rodney Dawes wrote:
On Sat, 2008-04-26 at 15:55 +0200, Vincent Untz wrote:
Hi,
I've asked for the creation of a git repository to host all fd.o specs
(will make things much easier). I think it'd make sense to send commit
notifications to this list
On Sat, 2008-04-26 at 15:55 +0200, Vincent Untz wrote:
Hi,
I've asked for the creation of a git repository to host all fd.o specs
(will make things much easier). I think it'd make sense to send commit
notifications to this list since it will help people track the progress
and the changes.
On Mon, 28 Apr 2008 11:41:50 +0200
Luca Cappelletti [EMAIL PROTECTED] wrote:
Hi,
On Sun, Apr 27, 2008 at 10:47 AM, [EMAIL PROTECTED] wrote:
This topic is may a bit OT: Why there is no open application
binary interface? I could use any binary on any operating system
which support this
well, the reason behind having all specs in one repo is to have them all
together, so that anyone wanting to do a change can get all of them from
the same place. Right now it seems to be hard to know where the source
of the spec is, so is there any way you could continue maintaining your
spec
On Tuesday 29 April 2008, Toni Ruottu wrote:
spec as you do now but have the latest version always in the shared git
repo?
That is how people usually work with distributed version control tools.
while this is awesome for source code where forking and working on branches is
good for obvious
Le mardi 29 avril 2008, à 21:43 +0300, Toni Ruottu a écrit :
Untz, do you have a reason for preferring GIT over Bazaar? I'm not
saying GIT is bad, I just want the choices to be discussed. We ought to
choose the one that best fits our needs.
I don't care that much about the vcs, to be honest.
you specifically *don't* want specifications to fork and be worked on
randomly; there is a low rate of edit conflict; having a clearly canonical
version is critical
Ok. It may be that dvcs would we a wrong solution for a real problem.
What I'm really concerned about is how hard it is
On Tuesday 29 April 2008, you wrote:
you specifically *don't* want specifications to fork and be worked on
randomly; there is a low rate of edit conflict; having a clearly
canonical version is critical
Ok. It may be that dvcs would we a wrong solution for a real problem.
What I'm
Hi Florent,
It is not really up to the application developper. It is more up to how
the JobViewer while behave on new jobs (i.e. will it pop up the jobview
window, will it behave silently with a notification icon...). So even if
it is not state literally in the spec, you'll not really have
10 matches
Mail list logo
