X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:sender:in-reply-to:references:date:message-id:subject
	:from:to:content-type;
	bh=NOOmMNNR7Wg/WK3iRyVA+vRVnDE8znaZTZitC/OlGAI=;
	b=oQNnpBJQwzDRlo/Dg1OUQvLvSKhOTcqMNiWitq/Bmq6NytA0Pq9TB5Hz/xg3iR4psD
	/rH90hK9Ie5YwRHhk4mM3YfiOOIpEOMHYkcVFUrSBCQdMzQMXT+p8BnEV7Up2AbpuPB2
	jI5olmmCtPy94pJVX9goP7kujZSJ8vTia1fPPB0MIC3kDzvcUd+BnrvkR7hvBYbtTuNC
	f5GhBUYtUIrcdEv1lLhK4m37oZUcFiReZZrUdetvGYSRcUKM78WfSvJIHwm8/tiLobgT
	a7YyBE7aT9mOAx3q45M2c/ctlTtlXdjsSEXXW8IQumw3WUW0IgcWzXk11Lxv37DNcEkz
	gfDA==
MIME-Version:	1.0
X-Received:	by 10.60.155.198 with SMTP id vy6mr10734733oeb.27.1442434138558;
	Wed, 16 Sep 2015 13:08:58 -0700 (PDT)
Sender:	svenn DOT bjerkem AT gmail DOT com
In-Reply-To:	<201509161954.t8GJsc80014424@envy.delorie.com>
References:	<alpine DOT DEB DOT 2 DOT 11 DOT 1509031356150 DOT 13201 AT nimbus>
	<55E8773B DOT 9000902 AT jump-ing DOT de>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509031846370 DOT 7163 AT nimbus>
	<55E8831A DOT 8050307 AT jump-ing DOT de>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509032004020 DOT 10628 AT nimbus>
	<55E891FA DOT 2010509 AT jump-ing DOT de>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509032039300 DOT 14871 AT nimbus>
	<55E8AE6C DOT 2090304 AT jump-ing DOT de>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509040031270 DOT 1962 AT nimbus>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509041040130 DOT 2971 AT nimbus>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1509162004460 DOT 3909 AT lichen>
	<55F9C1BF DOT 9030603 AT jump-ing DOT de>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1509162149180 DOT 24753 AT nimbus>
	<201509161954 DOT t8GJsc80014424 AT envy DOT delorie DOT com>
Date:	Wed, 16 Sep 2015 22:08:58 +0200
X-Google-Sender-Auth:	PYnH1tpDdAbt2nzKGJXTttHjX7Y
Message-ID:	<CAGde_xMK78S_P8=Gs3yR8SN57GnvDgW1ST0TP+2q+YXhbPCtUA@mail.gmail.com>
Subject:	Re: [geda-user] New experimental netlist features
From:	"Svenn Are Bjerkem (svenn DOT bjerkem AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user <geda-user AT delorie DOT com>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

--047d7bd904aa7101fd051fe2de45
Content-Type: text/plain; charset=UTF-8

On 16 September 2015 at 21:54, DJ Delorie <dj AT delorie DOT com> wrote:

>
> > Is there a technical reason for the "home/" prefix?  If not, I'd
> > prefer to just have "<username>/<topic>" as the branch name to keep
> > branch names short.
>
> Heh.  Reminds me of the home directory policy at my second job.
> Everyone had a home directory off of / that was named after their
> login.  One guy had a login of "dev" (it was his last name).  The
> system didn't work right after he cleaned up his "home" directory.
>


When doing a git branch -r, I see that there would probably be a need for a
prefix before the user/topic, otherwise the junior branches will be all
over the place. At Infineon we liked to use 'wk' as a short for 'work' as
the designflow tools were limited regarding length of path names. 'wk' will
also show up towards the bottom of the branch list. Maybe 'zz' will be even
better in that respect. Eventually they will become sleeping branches ....


-- 
Svenn

--047d7bd904aa7101fd051fe2de45
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
6 September 2015 at 21:54, DJ Delorie <span dir=3D"ltr">&lt;<a href=3D"mail=
to:dj AT delorie DOT com" target=3D"_blank">dj AT delorie DOT com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><span class=3D""><br>
&gt; Is there a technical reason for the &quot;home/&quot; prefix?=C2=A0 If=
 not, I&#39;d<br>
&gt; prefer to just have &quot;&lt;username&gt;/&lt;topic&gt;&quot; as the =
branch name to keep<br>
&gt; branch names short.<br>
<br>
</span>Heh.=C2=A0 Reminds me of the home directory policy at my second job.=
<br>
Everyone had a home directory off of / that was named after their<br>
login.=C2=A0 One guy had a login of &quot;dev&quot; (it was his last name).=
=C2=A0 The<br>
system didn&#39;t work right after he cleaned up his &quot;home&quot; direc=
tory.<br>
</blockquote></div><br><br></div><div class=3D"gmail_extra">When doing a gi=
t branch -r, I see that there would probably be a need for a prefix before =
the user/topic, otherwise the junior branches will be all over the place. A=
t Infineon we liked to use &#39;wk&#39; as a short for &#39;work&#39; as th=
e designflow tools were limited regarding length of path names. &#39;wk&#39=
; will also show up towards the bottom of the branch list. Maybe &#39;zz&#3=
9; will be even better in that respect. Eventually they will become sleepin=
g branches ....<br></div><br clear=3D"all"><br>-- <br><div class=3D"gmail_s=
ignature">Svenn</div></div>

--047d7bd904aa7101fd051fe2de45--

- Raw text -