I'm not a kicad dev, just an avid reader of the list, but I am pretty
fluent in git.
Here are some aliases that you might find useful (that go in your
~/.gitconfig)
[alias]
co = checkout
ci = commit
st = status
br = branch
hist = log --all --abbrev-commit --graph
This depends on which remote your local repo is linked to. I keep two
completely separate repos. One directly linked to the main kicad repo.
I use this one for patch merges and very minor changes. The result of
`git remote -v` for this repo looks like this:
origin
OK, I followed Seth’s recipe so I’m now “right-side-up”. (5.0 on master; 6.0
on a branch)
But I still don’t want to do a general push (as that will copy all my
branches), right?
So I do a:
git push origin master
right?
Next question, when it asks for my launchpad username, what’s it
Jeff,
Please remember no v6 stuff until the stable 5 version is released and
branched. If you muck it up, I can always overwrite it with the last
valid commit.
Cheers,
Wayne
On 03/02/2018 04:03 PM, Seth Hillbrand wrote:
Jeff-
As a fellow refuge from centralized VCSs, I sympathize. It
Jeff-
As a fellow refuge from centralized VCSs, I sympathize. It took me a while
to learn to love git branch but it is your friend.
Here's a quick way to get into the layout Wayne was recommending:
git checkout master (you are now in your branch that has all the V6 stuff)
git checkout -b
(to make this last point easier, you can configure git to automatically
rebase when you do `git pull` :
https://stevenharman.net/git-pull-with-automatic-rebase )
On Fri, Mar 2, 2018 at 3:46 PM, Wayne Stambaugh
wrote:
> Jeff,
>
> On 03/02/2018 03:28 PM, Jeff Young wrote:
>
Jeff,
On 03/02/2018 03:28 PM, Jeff Young wrote:
Before I go and make a hash of everything, can someone please validate
the following.
I have a bunch of 6.0 work on my master.
Making changes to master is risky unless you doing a simple bug fix but
even then I work in a separate branch then
> On Mar 2, 2018, at 10:28 AM, Andrzej Wolski wrote:
>
> Jon,
>
> I probably didn't express myself clearly. What I mean is a situation when
> *only* enabled layer if F.Paste and then you disable "Pads Front". Now
> nothing is visible on the board, but footprints are
Before I go and make a hash of everything, can someone please validate the
following.
I have a bunch of 6.0 work on my master.
I have a 5.0stable branch that I use for 5.0.
If I want to push changes for RC2, I’d do:
git push origin 5.0stable:master
Is that right?
Thanks,
Hi,
to be honest, I don’t really know what this is about.
@Andrey:
You looked for a very complex (foreign) project (Chris mainboard?) to prove
that eeschema is slow on Mac?
Well, we know that and we told you already some weeks/months ago why it is like
it is (if memory serves me right).
Or,
No, I agree with you in that case, that sounds like a bug in my patch and
I'll check it out this weekend when I can get back to coding.
Thanks,
Jon
On Fri, Mar 2, 2018 at 12:28 PM, Andrzej Wolski
wrote:
> Jon,
>
> I probably didn't express myself clearly. What I mean
Jon,
I probably didn't express myself clearly. What I mean is a situation
when *only* enabled layer if F.Paste and then you disable "Pads Front".
Now nothing is visible on the board, but footprints are still selectable.
In other words, when no single item belonging to footprint is visible,
> On Mar 1, 2018, at 8:53 PM, Seth Hillbrand wrote:
>
> Andrey-
>
> I'm moving this to a new thread so that we don't conflate the OpenMP
> discussion with this.
>
> Can you test running Kicad with the "Open in Low Resolution" mode enabled?
> You can activate this
Hi Andrey,
I just tried some and I didn't see a large difference in zoom behavior
between eeschema and pcbnew. They do use different zoom mechanisms when
you use Modern toolset in PcbNew, but the difference is minor.
Eeschema is not hardware-accelerated so I would expect that running it in
low
On 01/03/18 20:15, Wayne Stambaugh wrote:
> Please
> congratulate Jon Evans, Seth Hillbrand, and Jeff Young for their
> promotion to the lead developers team.
Congratulations gentlemen! Let's make KiCad great together!
Tom
___
Mailing list:
Hi Andrzej,
This was my intention, which is why I said I was prepared for other people
to have other opinions :-)
I think that you should still be able to select footprints even if the
"front pads" is hidden from layers like the paste layer, *unless* you are
in high contrast mode.
-Jon
On Fri,
Congratulations! I am very glad to see this! I have been following the
mailing list for a while now and seen the great contributions and ideas
from you guys! Well deserved promotion!
-Kristoffer
On 2018-03-02 15:05, David Novak wrote:
Great job guys! Thanks for your investment in the
Great job guys! Thanks for your investment in the project.
David
On 3/2/2018 2:40 AM, Maciej Sumiński wrote:
Congratulations fellow developers! You have received well deserved
promotions, and I am glad to see your names in the
kicad-product-committers group. Keep on rocking!
Cheers,
Orson
LOL, I just replied to Miles. Thanks Orson for helping out!
On 3/2/2018 8:36 AM, Maciej Sumiński wrote:
> Hi Miles,
>
> I suppose the silence in the thread indicates there are not many
> developers knowing the Python scripting interface inside out. Since you
> are both studying the scripting
Miles,
I wish I had a answer for your but you are probably on your own here
unless the developer who implemented this steps in and helps. I don't
have the time to figure it out right now. Maybe someone else can help
you or maybe you could become the resident python expert and maintain
this. ;)
Hi Miles,
I suppose the silence in the thread indicates there are not many
developers knowing the Python scripting interface inside out. Since you
are both studying the scripting interface and developing own scripts, it
is quite possible you are the most competent person to give us an advice
on
Thank you Andrzej, I have just merged your patch.
Cheers,
Orson
On 03/02/2018 01:52 AM, Andrzej Wolski wrote:
> I'm resending a patch from this thread:
> https://lists.launchpad.net/kicad-developers/msg34285.html
>
> I believe it should go into rc2?
>
> State of some recently added checkboxes
On 02.03.2018 06:52, Andrey Kuznetsov wrote:
> Thank you to someone on the dev team I guess for getting rid of the mouse
> warp events from right click, however the zoom mouse warp to the center of
> the screen is still a major WTF.
That is an option in preferences -> general -> pan and zoom
I've tried this patch, and there is a small issue: if you have only eg
front paste layer enabled and front pads are hidden, footprint is still
selectable.
Andrzej
W dniu 2018-02-27 o 04:11, Jon Evans pisze:
This patch changes the selection logic for footprints to fix a
reported issue[1] and
24 matches
Mail list logo