>
> Julien Puydt > writes:
> > Le 31/08/2012 00:19, Robert Bradshaw a écrit :
> >> On Thu, Aug 30, 2012 at 12:17 PM, David
> >> Roe>
> wrote:
> What in particular was bothersome about github?
> >
> >> Issue-tracking in particular is sub-par on github (though I've heard
> >> they've b
Julien Puydt writes:
> Le 31/08/2012 00:19, Robert Bradshaw a écrit :
>> On Thu, Aug 30, 2012 at 12:17 PM, David Roe wrote:
What in particular was bothersome about github?
>
>> Issue-tracking in particular is sub-par on github (though I've heard
>> they've been working on this), and having t
Le 31/08/2012 00:19, Robert Bradshaw a écrit :
On Thu, Aug 30, 2012 at 12:17 PM, David Roe wrote:
What in particular was bothersome about github?
Issue-tracking in particular is sub-par on github (though I've heard
they've been working on this), and having to both is a pain. There's
also the
On Thu, Aug 30, 2012 at 12:17 PM, David Roe wrote:
>>
>> What in particular was bothersome about github?
>
> I don't remember all the details, but I think having to deal with both
> trac and github got very tiresome. We don't want to move completely
> to github since we have a bunch of existing t
>
> What in particular was bothersome about github?
I don't remember all the details, but I think having to deal with both
trac and github got very tiresome. We don't want to move completely
to github since we have a bunch of existing tickets and progress on
trac. So we decided to try making git
On 8/30/12 1:20 PM, Keshav Kini wrote:
Jason Grout writes:
On 8/30/12 1:10 PM, Julien Puydt wrote:
Le 30/08/2012 19:51, Jason Grout a écrit :
If/when we move to github or to bitbucket or something, where people can
easily push their own branches, it will be much more natural to push
your in-p
Jason Grout writes:
> On 8/30/12 1:10 PM, Julien Puydt wrote:
>> Le 30/08/2012 19:51, Jason Grout a écrit :
>>> If/when we move to github or to bitbucket or something, where people can
>>> easily push their own branches, it will be much more natural to push
>>> your in-progress code up and collabo
On Thursday, August 30, 2012 1:52:17 PM UTC-4, jason wrote:
>
>
> I post in-progress code to trac because:
>
> 1. It's a backup of the code. There has been several times when I
> wanted to go back to an old patch and work on it more, but the only
> place I could find it was a copy I had put u
On 8/30/12 1:10 PM, Julien Puydt wrote:
Le 30/08/2012 19:51, Jason Grout a écrit :
If/when we move to github or to bitbucket or something, where people can
easily push their own branches, it will be much more natural to push
your in-progress code up and collaborate.
*IF* !?
Progress seems to
Le 30/08/2012 19:51, Jason Grout a écrit :
If/when we move to github or to bitbucket or something, where people can
easily push their own branches, it will be much more natural to push
your in-progress code up and collaborate.
*IF* !?
Snark on #sagemath
--
You received this message because yo
On 2012-08-30 19:51, Jason Grout wrote:
> I post in-progress code to trac because:
>
> 1. It's a backup of the code. There has been several times when I
> wanted to go back to an old patch and work on it more, but the only
> place I could find it was a copy I had put up on trac.
> 2. It lets othe
On 8/30/12 12:42 PM, Luis Finotti wrote:
Firstly, thanks all for the replies.
On Thursday, August 30, 2012 12:54:31 PM UTC-4, Simon King wrote:
Hi Luis,
On 2012-08-30, Michael Orlitzky >
wrote:
>
> In general, if you're trying to sidestep the mercurial workflow,
Firstly, thanks all for the replies.
On Thursday, August 30, 2012 12:54:31 PM UTC-4, Simon King wrote:
>
> Hi Luis,
>
> On 2012-08-30, Michael Orlitzky >
> wrote:
> >
> > In general, if you're trying to sidestep the mercurial workflow, ...
>
> Are you? It seems to me that following the mercur
On Aug 30, 9:54 am, Simon King wrote:
> Do "hg qimport /path/to/my.patch"
> * The previous command was importing the patch, but not *applying* it.
> Hence, do "hg qpush"
> * Rebuild your new Sage version ("../../sage -br" or so)
I found the abbreviation
hg qimport -P ...
to combine the
Hi Luis,
On 2012-08-30, Michael Orlitzky wrote:
> On 08/30/2012 12:36 PM, Luis Finotti wrote:
>> Dear all,
>>
>> I had some changes made in a older version of sage. I wanted to create
>> a patch that I can apply to a new install, without uploading to trac (as
>> the changes are not "good enough
On 8/30/12 11:36 AM, Luis Finotti wrote:
Dear all,
I had some changes made in a older version of sage. I wanted to create
a patch that I can apply to a new install, without uploading to trac (as
the changes are not "good enough"). Can anyone tell me the necessary
commands or point me in the ri
16 matches
Mail list logo
