On Mon, Nov 7, 2016 at 5:59 PM, René J.V. Bertin
wrote:
> >The problem with these headers is they force VC to do a lot more work to
>
> VC?
Version control. *Any* version control. RCS and CVS (and before them SCCS)
used, and hacked around, keywords. SVN made most of them
On Monday November 07 2016 16:04:00 Brandon Allbery wrote:
>The problem with these headers is they force VC to do a lot more work to
VC?
>determine when two files are "the same". It's not just a matter of
>convenience; if you do not either hook into git's diff mechanism or be
>*extremely*
On Mon, Nov 7, 2016 at 3:54 AM, René J. V. Bertin
wrote:
> Re: $Id$ headers: I found them quite useful as a quick an unambiguous way
> to
> compare file versions chronologically. Isn't there a way to bring this
> back with
> a pre-commit hook and possibly `git
Hi,
On Mon, Nov 07, 2016 at 09:25:40PM +0100, Lawrence Velázquez wrote:
> src/macports1.0/macports.tcl | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/src/macports1.0/macports.tcl b/src/macports1.0/macports.tcl
> index 14d628f..6aafa73 100644
> ---
> On Nov 7, 2016, at 12:39 PM, Lawrence Velázquez wrote:
>
>> On Nov 7, 2016, at 12:29 PM, René J.V. Bertin wrote:
>>
>> As long as it doesn't cause problems elsewhere I think there
>> shouldn't be any hard rules making this kind of thing impossible.
> On Nov 7, 2016, at 12:29 PM, René J.V. Bertin wrote:
>
>> On Monday November 07 2016 11:52:17 Lawrence Velázquez wrote:
>>
>> Any sort of Git keyword expansion must happen client-side, which means
>> such keywords/markers would only be useful to developers who choose to
On Monday November 07 2016 11:52:17 Lawrence Velázquez wrote:
> Any sort of Git keyword expansion must happen client-side, which means
> such keywords/markers would only be useful to developers who choose to
> configure their local repositories appropriately, which means that they
> can never be
> On Nov 5, 2016, at 1:03 PM, Marko Käning wrote:
>
>> On 04 Nov 2016, at 19:00 , Lawrence Velázquez wrote:
>>
>> Sure. I would encourage committers who want feedback to open as many PRs
>> as they want.
>>
>> (You get a PR! You get a PR! Everybody
> On Nov 7, 2016, at 10:37 AM, Rainer Müller wrote:
>
> Multiple of the affected ports just change the '.cmd' to 'autogen.sh'.
> Would it make sense to have an additional use_autogensh that defaults to
> this and adds dependencies on autoconf, automake, libtool?
This is a
On 2016-11-07 12:13, Mihai Moldovan wrote:
> Mihai Moldovan (Ionic) pushed a commit to branch master
> in repository macports-ports.
>
> https://github.com/macports/macports-ports/commit/ce3e478b4aa910e128b737ff7523242ec6e63536
>
> The following commit(s) were added to refs/heads/master by this
10 matches
Mail list logo