On Sun, 11 Oct 2015 at 10:42 Barry Warsaw wrote:
> What I've done, and it's probably horrible, is to just `git-dpm tag
> --refresh`
> and then `git push --tags --force`.
>
That does look yuck.
If my vague understanding is correct, it seems that git-dpm wants to assign
the tags to the same commi
On Sun, 11 Oct 2015 at 13:50 Brian May
wrote:
> I just converted and pushed these branches to git-dpm.
>
>
Just noticed how it named the upstream branches.
* [new branch] upstream-debian/experimental -> upstream-debian/experimental
* [new branch] upstream-debian/jessie -> upstream-debian/jessie
On Sun, 11 Oct 2015 at 11:40 Brian May
wrote:
> Should we convert all branches to git-dpm? Or forget the branches
> referring to obsolete distributions?
>
> Probably should do these:
>
> origin/debian/experimental
> origin/debian/jessie
> origin/debian/sid
>
I just converted and pushed these bra
Should we convert all branches to git-dpm? Or forget the branches referring
to obsolete distributions?
Probably should do these:
origin/debian/experimental
origin/debian/jessie
origin/debian/sid
Not sure about these
origin/debian/squeeze
origin/debian/wheezy
origin/debian/wheezy-backports
Of c
On Sat, 10 Oct 2015 at 09:55 Barry Warsaw wrote:
> Probably so. I have a checkout of python-django here and it seems to
> already
> be in git. I haven't looked at the converted svn->git repo yet, but I'm
> wondering if what was converted was just old and out of date? I'm pretty
> sure
> it was
On Sat, 10 Oct 2015 at 09:54 Brian May
wrote:
> We can move the migrated version out of the way, restore the old version,
> and update it to the required standards (e.g. git-dpm). Is everyone happy
> with this approach?
>
Have moved the repository back. Should be usable exactly as before. Have
n
On Oct 10, 2015, at 04:19 AM, Brian May wrote:
>According to the wiki I do this with the following command:
>
>brian@prune:~/tree/debian/python-modules/django-ajax-selects$ git-dpm tag
>git-dpm: ERROR: tag 'upstream/1.3.6' already exists and differs!
>
>This wasn't the response I was expecting. I
On 10/10/2015 12:16 AM, Brian May wrote:
> On Sat, 3 Oct 2015 at 00:24 Barry Warsaw wrote:
>
>> 5-Oct - Do one last test run with an updated svn dump. Put the results in
>> a
>> public place for folks to play with and comment on.
>>
>> 8-Oct - Assuming no objections or showstoppers, turn off wri
On Oct 10, 2015, at 12:18 PM, Ben Finney wrote:
>You need to specify which username to connect to over SSH. I have
>updated the Wiki page above to clarify this.
Hmm, I'm not sure about this recommendation. I don't include my user name in
the url, and I'm pretty sure Mattia's suggestion to set th
Hi Piotr and others,
Since the git transition seems to be done, how about adding me to the
debian python teams so I can create the repos on Alioth and push my work
so far to them?
@Matthias:
Call by name *shudder*, remember having to work with some Fortran code
using call by name in my physics ti
On Oct 10, 2015, at 09:13 AM, Raphael Hertzog wrote:
>Yes, except for the naming of branches where I would prefer to keep the
>DEP-14 naming scheme (we should just rename debian/sid into debian/master).
>
>http://dep.debian.net/deps/dep14/
>
>And I would suggest that we generalize the DEP-14 namin
Hi,
On Fri, 09 Oct 2015, Brian May wrote:
> We can move the migrated version out of the way, restore the old version,
> and update it to the required standards (e.g. git-dpm). Is everyone happy
> with this approach?
Yes, except for the naming of branches where I would prefer to keep
the DEP-14 na
12 matches
Mail list logo