All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Checking out and comitting to the libsensors-3.x branch
Date: Mon, 02 Apr 2007 08:17:41 +0000	[thread overview]
Message-ID: <4610BC25.8050507@hhs.nl> (raw)

Hi,

I've been really busy lately with Fedora related "work", but I hope to find the 
time soon to start working on the dyn chip support. Most of the code is already 
tehre for the 2.x branch (written by my students). ANd my initial testing was good.

This leads me to the following questions:
1) What cmdline magic must I pass to svn to get the 3.x branch when checking
    out?
2) Do I need any cmdline magic to make sure a commit goes to the 3.x branch?
    (I've bad experiences with this with CVS, where a commit would go to the
     default branch even though I checkout another)
3) Is it ok for me to just start committing this, or should I post it for
    review here first?

Thanks & Regards,

Hans



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

             reply	other threads:[~2007-04-02  8:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-02  8:17 Hans de Goede [this message]
2007-04-02 11:36 ` [lm-sensors] Checking out and comitting to the libsensors-3.x Jean Delvare
2007-04-02 12:01 ` Axel Thimm
2007-04-03 13:15 ` Mark M. Hoffman
2007-04-04 19:29 ` Jean Delvare
2007-04-04 19:43 ` Axel Thimm
2007-04-05 20:15 ` Jean Delvare
2007-04-05 20:31 ` Axel Thimm
2007-04-08  8:14 ` Jean Delvare
2007-04-08  8:33 ` Axel Thimm
2007-04-08 17:40 ` Jean Delvare
2007-04-10 14:23 ` Jean Delvare
2007-04-10 14:43 ` Axel Thimm
2007-04-12  9:12 ` Jean Delvare
2007-04-20 13:17 ` Jean Delvare
2007-04-22 19:03 ` Axel Thimm
2007-04-23 11:53 ` Jean Delvare

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=4610BC25.8050507@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.