> On Oct 24, 2016, at 7:03 PM, Michael wrote:
>
>> On 2016-10-24, at 2:57 PM, Marko Käning wrote:
>>
>> Well, but I think what you, Michael, are describing, is only needed
>> if you work with many patches which aren’t really committed to any
>>
Hi,
On Tue, Oct 25, 2016 at 12:17:57AM +0200, Marko Käning wrote:
> A description of how exactly one would rebase (potentially squash and
> history-rewrite) a submitted PR onto current master should be on our
> WorkingWithGit wiki page.
the easiest approach is just clicking the button that does
On 2016-10-24, at 2:57 PM, Marko Käning wrote:
> Hi folks,
>
> when I read only the first two paragraphs of this thread...
>
> On 24 Oct 2016, at 18:37 , Michael wrote:
>> So since MacPorts is moving to git, and from what I saw in the "how to use
I fully agree with Mojca, that it is better to work on a private fork for the
start and let others - like Clemens suggested - take part in reviewing on that
forked repository. This way one can train what would have to be done on the
main macports-ports repo before causing trouble there...
On
On Mon, Oct 24, 2016 at 11:57:51PM +0200, Marko Käning wrote:
> The only question mark I have there is:
>
> Will we ask the committers to squash their changesets or prefer to
> clutter the main repo with potentially many tiny iterations for the
> changed ports??
I think
> On Oct 24, 2016, at 5:57 PM, Marko Käning wrote:
>
> The only question mark I have there is:
>
> Will we ask the committers to squash their changesets or prefer
> to clutter the main repo with potentially many tiny iterations
> for the changed ports??
Hi folks,
when I read only the first two paragraphs of this thread...
On 24 Oct 2016, at 18:37 , Michael wrote:
> So since MacPorts is moving to git, and from what I saw in the "how to use
> git" docs you mentioned, you apparently want people to work with patchsets
>
Hi René,
On 24 Oct 2016, at 09:57 , René J.V. Bertin wrote:
> On Monday October 24 2016 09:54:56 Marko Käning wrote:
>
> Indirectly, yes. I get the impression port:opencv has been unmaintained for a
> while, so maybe you can update the official copy from mine?
I’ve added
On Mon, Oct 24, 2016 at 08:22:38PM +0200, Mojca Miklavec wrote:
> Even if the method of achieving this is not prescribed***, I wouldn't
> mind a bit of testing before screwing up the real repository.
>
> *** But having some cheatsheet would help.
Sure, feel free to create a fork, play around,
>
> You should check with the developers of Coda on their Git support. I
> don't think a tool built especially for website editing will be the best
> choice, but maybe it works for you.
Otherwise I also use PyCharm free edition for some Python related tasks, and it
seems to have built-in GitHub
On 2016-10-24 20:24, Daniel J. Luke wrote:
> On Oct 24, 2016, at 1:26 PM, Clemens Lang wrote:
>> On Mon, Oct 24, 2016 at 12:54:23PM -0400, Daniel J. Luke wrote:
>>> This looks like it's true for me as well (cannot edit tickets beyond
>>> making comments).
>>
>> Try clearing
On Oct 24, 2016, at 1:26 PM, Clemens Lang wrote:
> On Mon, Oct 24, 2016 at 12:54:23PM -0400, Daniel J. Luke wrote:
>> This looks like it's true for me as well (cannot edit tickets beyond
>> making comments).
>
> Try clearing your cache (a force-reload should do that). It seems
On 24 October 2016 at 20:08, Lawrence Velázquez wrote:
>> On Oct 24, 2016, at 1:58 PM, Clemens Lang wrote:
>>> On Mon, Oct 24, 2016 at 07:47:18PM +0200, Mojca Miklavec wrote:
>>>
>>> (My preference would be to keep linear history for master and not to
>>> keep ten broken revisions of a Portfile
> On Oct 24, 2016, at 1:58 PM, Clemens Lang wrote:
>
> I don't think we should mandate a complex "run these magic git commands"
> workflow. Making things complicated will just make them go wrong.
Agreed.
>> On Mon, Oct 24, 2016 at 07:47:18PM +0200, Mojca Miklavec wrote:
>>
> I think Michael is thinking:
>
> I have port 'foo' in macports and it requires a (rather large/complicated)
> patch that currently sits in files/ and has to be re-generated every time
> upstream releases a new version of 'foo'
>
> And essentially we're saying "we haven't done anything to
Hi,
On Mon, Oct 24, 2016 at 08:00:04PM +0200, Vincent Habchi wrote:
> I’ve bought Coda 2 when I use to do a bit of HTML development. Can I
> use it to check out - tinker with the new MacPorts GIT repository?
You should check with the developers of Coda on their Git support. I
don't think a tool
> On Oct 24, 2016, at 2:00 PM, Vincent Habchi wrote:
>
> I’ve bought Coda 2 when I use to do a bit of HTML development. Can
> I use it to check out - tinker with the new MacPorts GIT repository?
You can use any Git client you like, as long as you're aware that we'll
Guys,
I’ve bought Coda 2 when I use to do a bit of HTML development. Can I use it to
check out - tinker with the new MacPorts GIT repository?
TIA,
Vincent
___
macports-dev mailing list
macports-dev@lists.macosforge.org
On Mon, Oct 24, 2016 at 07:47:18PM +0200, Mojca Miklavec wrote:
> I can send you a screenshot comparing the version I opened two hours
> ago and the same page reloaded just now. The result changed in the
> meantime. In any case I can no longer provide you any broken example
> (there are still some
On Oct 24, 2016, at 1:39 PM, Clemens Lang wrote:
> On Mon, Oct 24, 2016 at 10:29:19AM -0700, Michael wrote:
>> My understanding -- and maybe this is my error here -- is that your
>> patches have to be constantly rebased onto the current version every
>> time the upstream
On 24 October 2016 at 19:15, Lawrence Velázquez wrote:
>> On Oct 24, 2016, at 12:50 PM, Mojca Miklavec wrote:
>>
>> (not?) related to the above question: One thing I'm confused about is
>> that whenever I'm listed as a reporter or in CC, my name would be
>> replaced by all the three data (my
Hi,
On Mon, Oct 24, 2016 at 10:29:19AM -0700, Michael wrote:
> My understanding -- and maybe this is my error here -- is that your
> patches have to be constantly rebased onto the current version every
> time the upstream releases a new version.
I think our understanding of what "upstream" is in
On Oct 24, 2016, at 12:29, Michael wrote:
>
>
>> On 2016-10-24, at 10:25 AM, Clemens Lang wrote:
>>
>> Hi,
>>
>>> On Mon, Oct 24, 2016 at 09:37:37AM -0700, Michael wrote:
>>> So since MacPorts is moving to git, and from what I saw in the "how to
>>>
> On Oct 24, 2016, at 12:15, Lawrence Velázquez wrote:
>
> The "macports-ports" repository
> (https://github.com/macports/macports-ports.git) already contains
> a stale version of the ports tree; you can fork it and play around with
> it as you wish.
If you clone or fork
Hi,
On Mon, Oct 24, 2016 at 06:50:47PM +0200, Mojca Miklavec wrote:
> Is that true also for any other email we used prior to becoming
> committers?
Yes.
> Can new emails be added later?
Yes, but you'll have to relogin.
> How exactly does it work when people enter multiple emails? (Judging
>
On 2016-10-24, at 10:25 AM, Clemens Lang wrote:
> Hi,
>
> On Mon, Oct 24, 2016 at 09:37:37AM -0700, Michael wrote:
>> So since MacPorts is moving to git, and from what I saw in the "how to
>> use git" docs you mentioned, you apparently want people to work with
>> patchsets
Hi,
On Mon, Oct 24, 2016 at 09:37:37AM -0700, Michael wrote:
> So since MacPorts is moving to git, and from what I saw in the "how to
> use git" docs you mentioned, you apparently want people to work with
> patchsets rebased onto the current head from upstream.
>
> As I was thinking about that,
> On Oct 24, 2016, at 12:50 PM, Mojca Miklavec wrote:
>
>> On 21 October 2016 at 20:12, Clemens Lang wrote:
>>
>> Action Required: GitHub Accounts
>>
>> Our new Trac installation will use GitHub for login. If you do not have
>> a GitHub
On Oct 23, 2016, at 12:02 AM, Joshua Root wrote:
> On 2016-10-23 14:48 , Jeremy Huddleston Sequoia wrote:
>> I still cannot edit tickets (beyond making comments). My @macports.org
>> email address was on my github account months ago, so that's not the issue.
>
> The problem
Hi,
On 21 October 2016 at 20:12, Clemens Lang wrote:
>
> Action Required: GitHub Accounts
>
> Our new Trac installation will use GitHub for login. If you do not have
> a GitHub account yet, please create one now at
> https://github.com/join
>
> To help us match
So since MacPorts is moving to git, and from what I saw in the "how to use git"
docs you mentioned, you apparently want people to work with patchsets rebased
onto the current head from upstream.
As I was thinking about that, I realized that you lose your history of the
patchset in the process.
> On Oct 24, 2016, at 6:56 AM, Mojca Miklavec wrote:
>
> On 20 October 2016 at 10:41, Mojca Miklavec wrote:
>> On 20 October 2016 at 04:42, Joshua Root wrote:
>>> On 2016-10-20 13:23 , Ryan Schmidt wrote:
> On Oct 19, 2016, at 9:04 PM, mo...@macports.org
On 20 October 2016 at 10:41, Mojca Miklavec wrote:
> On 20 October 2016 at 04:42, Joshua Root wrote:
>> On 2016-10-20 13:23 , Ryan Schmidt wrote:
>>>
>>>
On Oct 19, 2016, at 9:04 PM, mo...@macports.org wrote:
Revision
154081
Author
mo...@macports.org
Date
On Monday October 24 2016 09:54:56 Marko Käning wrote:
Indirectly, yes. I get the impression port:opencv has been unmaintained for a
while, so maybe you can update the official copy from mine?
>I think I already let you know, that this did the job! :)
>
>
>
>
>On 21 Oct 2016, at 01:54 , René
34 matches
Mail list logo