public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Sending in patches
Date: Fri, 29 Jan 2016 02:13:40 +0000	[thread overview]
Message-ID: <1454033620.585.214.camel@ipfire.org> (raw)
In-Reply-To: <op.ybylvwklcahio0@honk.fritz.box>

[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]

Hi,

On Thu, 2016-01-28 at 18:36 +0100, Larsen wrote:
> On Sun, 17 Jan 2016 20:17:22 +0100, Michael Tremer  
> <michael.tremer(a)ipfire.org> wrote:
> 
> > On Sat, 2016-01-16 at 19:07 +0100, Larsen wrote:
> > > On Fri, 15 Jan 2016 02:25:43 +0100, Michael Tremer
> > > <michael.tremer(a)ipfire.org> wrote:
> > > 
> > > > I didn't know that this many people use Windows. The problem
> > > > with
> > > > that
> > > > is you cannot build the distribution. You can copy some files
> > > > back
> > > > and
> > > > forth, but never build.
> > > > 
> > > > I consider this to be a huge disadvantage.
> > > > 
> > > > Is this just by choice or did you not want to go through the
> > > > trouble
> > > > setting up a Linux system?
> > > 
> > > Till now, I only wanted to improve things where I didn't need to
> > > build the
> > > distribution. Otherwise, I would probably have setup a Linux VM.
> > > 
> > > 
> > > > When ever you make personal notes, why not use the wiki for
> > > > that
> > > > and
> > > > share? Many other people might have the same questions.
> > > 
> > > Ok, will see to get the stuff into the wiki. Into which article
> > > should I
> > > put it?
> > 
> > Split the content in small and topical pages in the namespace where
> > the
> > other ones are already.
> 
> here it is:
> http://wiki.ipfire.org/devel/tortoisegit

Great. I moved this into the Git sub-section:

  http://wiki.ipfire.org/devel/git/windows

I didn't test if this actually works because I do not use Windows.

Best,
-Michael

> 
> 
> Lars

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-01-29  2:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 21:54 Michael Tremer
2016-01-11 20:40 ` Larsen
2016-01-15  1:25   ` Michael Tremer
2016-01-15  8:07     ` IT Superhack
2016-01-15 19:24       ` R. W. Rodolico
2016-01-16 14:45         ` Michael Tremer
2016-01-16 16:07         ` Matthias Fischer
2016-01-16 14:48       ` Michael Tremer
2016-01-16 18:07     ` Larsen
2016-01-17 19:17       ` Michael Tremer
2016-01-28 17:36         ` Larsen
2016-01-29  2:13           ` Michael Tremer [this message]
2016-01-12 18:08 ` Matthias Fischer
2016-01-15  1:28   ` Michael Tremer
     [not found] <DUB406-EAS128B6703A1A0778E8A258779CC90@phx.gbl>
2016-01-12 23:51 ` Michael Tremer
2016-01-13  4:39   ` Xaver4all
2016-01-15  1:29     ` Michael Tremer
     [not found] <DUB406-EAS163F3237DC6DE1AF244CD409CCE0@phx.gbl>
2016-01-16 14:53 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1454033620.585.214.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox