Re: How to keep uncommitted work in a git clone

[David Bariod]

On Fri, Nov 4, 2016 at 10:20 AM, Chris Jones <jon...@hep.phy.cam.ac.uk>
wrote:

> Hi,
>
> On 04/11/16 09:16, David Bariod wrote:
>
>>
>>
>> On Fri, Nov 4, 2016 at 9:55 AM, Chris Jones <jon...@hep.phy.cam.ac.uk
>> <mailto:jon...@hep.phy.cam.ac.uk>> wrote:
>>
>>
>>
>> On 04/11/16 05:39, David Bariod wrote:
>>
>> Hello,
>>
>> Personnally, I would just commit such change. It is cheap, can be
>> reworked later and be ketp safe in a private remote repository
>> in case
>> of disaster.
>> With git there are no reason to not commit event not ready yet
>> change set.
>>
>>
>> I would not do this, as you then might end up with a lot of
>> intermediary commits in the history. better I think to work on
>> independent projects on independent branches.
>>
>>
>> Then you can do a git rebase -i to clean up when you want to publish
>> your final state.
>>
>
> Still, if you have independent pieces of work in progress, its still
> better IMHO to separate them into branches. The policy of not working on
> the master with git is not my idea, its a widely held piece of (good)
> advice, for various reasons.
>

Yes, using different branch is definitely a good idea

David
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: How to keep uncommitted work in a git clone

[David Bariod]

On Fri, Nov 4, 2016 at 9:55 AM, Chris Jones <jon...@hep.phy.cam.ac.uk>
wrote:

>
>
> On 04/11/16 05:39, David Bariod wrote:
>
>> Hello,
>>
>> Personnally, I would just commit such change. It is cheap, can be
>> reworked later and be ketp safe in a private remote repository in case
>> of disaster.
>> With git there are no reason to not commit event not ready yet change set.
>>
>
> I would not do this, as you then might end up with a lot of intermediary
> commits in the history. better I think to work on independent projects on
> independent branches.
>

Then you can do a git rebase -i to clean up when you want to publish your
final state.

David
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: advanced bash-ing for long compiles

[David Bariod]

Hi Ken,

I would really use screen instead and disconnect it and reconnect it later.

David

On Fri, Oct 14, 2016 at 4:30 PM, Ken Cunningham <
ken.cunningham.web...@gmail.com> wrote:

> Some advice appreciated ...
>
>
> long compiles can take hours
>
> i can ssh into the machine and get it started
>
> sudo port -v install gcc48 gcc5 gcc6 gcc7
>
> that, for example, might take several days to finish (if it does finish)
>
> then I control-Z to pause it, and "bg" to throw it into the background
>
> then I can close my ssh session and the compile proceeds...
>
> how exactly do I best find that process to "fg" it again? If I just log
> back in and "fg" it, it is not found. but top shows the process is humming
> away in the background, as expected
>
> is the process different from a local shell vs a remote shell?
> is this all wrong, and it's way better to use screen or tmux or ???
>
> Thanks,
>
> K
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: tcl question: defining dynamically named variables in a namespace

[David Bariod]

It's been a long time I haven't done Tcl development, but from memory:

namespace eval  {
 --> your code here <---
}

should do what you're trying to do.

--
David

On Fri, Oct 7, 2016 at 2:12 PM, René J.V. Bertin 
wrote:

> sorry for the noise, it seems I can simply use
>
> namespace upvar kf5 ${name}_dep dep
>
> etc.
>
> Now, would it be possible and worth the trouble to put
> kf5.framework_dependency procedure itself into the dedicated namespace?
>
> R.
> ___
> macports-dev mailing list
> macports-dev@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev
>
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: How to use git

[David Bariod]

On Mon, Aug 22, 2016 at 10:57 AM, Mojca Miklavec  wrote:

> On 20 August 2016 at 02:19, Ryan Schmidt wrote:
> >
> > https://trac.macports.org/wiki/WorkingWithGit
>
> We should add this:
> http://stackoverflow.com/questions/927358/how-to-undo-
> last-commits-in-git#927386
> to:
> https://trac.macports.org/wiki/WorkingWithGit#revert
>
> Currently the third paragraph sounds scary and it doesn't have to be.
>
> I use "git reset HEAD~" all the time to fix commit messages or to fix
> whatever I screwed up in the last commit.
>

Don't you find git commit --amend easier for such purpose ?

--
David
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev