Le dimanche, 11 novembre 2012 10.25:05, Thomas Koch a écrit :
> .oO(One day all maintainers will use Git... :-)
… the same way, of course.
OdyX
signature.asc
Description: This is a digitally signed message part.
Thomas Koch writes:
> Ansgar Burchardt:
>> Thomas Koch writes:
>> > For every debian source package that enters the archive, dak should
>> > commit the source code to a public readable Git repository and put a
>> > signed tag on it.
>>
>> I do not think that is a good idea:
>>
>> You would end
Ansgar Burchardt:
> Thomas Koch writes:
> > For every debian source package that enters the archive, dak should
> > commit the source code to a public readable Git repository and put a
> > signed tag on it.
>
> I do not think that is a good idea:
>
> You would end with two repositories for packa
On 08/11/2012 11:26, Paul Wise wrote:
> On Wed, Nov 7, 2012 at 4:36 PM, Thomas Koch wrote:
>
>> For every debian source package that enters the archive, dak should commit
>> the
>> source code to a public readable Git repository and put a signed tag on it.
>
> While we are discussing wacky ideas
On Wed, Nov 7, 2012 at 4:36 PM, Thomas Koch wrote:
> For every debian source package that enters the archive, dak should commit the
> source code to a public readable Git repository and put a signed tag on it.
While we are discussing wacky ideas, there is a derivative putting the
entire installed
[ not implying that the original idea of importing packages
automatically into git is necessarily a good one.. however.. ]
On 11/07/2012 05:09 PM, Tollef Fog Heen wrote:
>> We have the same trouble with snapshot.debian.org, and Alioth, no?
>
> No, since we can black out packages there in the rare
On Wed, 07 Nov 2012, Ansgar Burchardt wrote:
> It has the same problems with non-free files in the history as 3.0
> (git). Actually worse as the maintainer cannot remove parts of the
> history in a later upload.
in such cases just 'git filter-branch' that repository, and replace with
a filtered
]] Thomas Goirand
> > It has the same problems with non-free files in the history as 3.0
> > (git). Actually worse as the maintainer cannot remove parts of the
> > history in a later upload.
>
> We have the same trouble with snapshot.debian.org, and Alioth, no?
No, since we can black out packa
On 11/07/2012 05:21 PM, Ansgar Burchardt wrote:
> Thomas Koch writes:
>> For every debian source package that enters the archive, dak should commit
>> the
>> source code to a public readable Git repository and put a signed tag on it.
+1
I would use such service!
> I do not think that is a good
Thomas Koch writes:
> For every debian source package that enters the archive, dak should commit
> the
> source code to a public readable Git repository and put a signed tag on it.
I do not think that is a good idea:
You would end with two repositories for packages maintained in Git.
It has t
Le Wed, Nov 07, 2012 at 09:36:39AM +0100, Thomas Koch a écrit :
> Hi Michael, Zack, et al,
>
> thank you Michael for codesearch. Since somebody asked about code browsing
> and
> Zack is interested in some source.debian.org I wanted to mention my dream:
>
> For every debian source package that e
11 matches
Mail list logo
